any news regard this topic ?
I use Maven 2 to build, run TestNG test cases, and deploy a Seam .war to JBoss. In order to deploy to Glassfish, I would think that you merely need to figure out how you're going to package your Seam application and how you will deploy it (I use a simple file copy approach to copy the .war into the deploy directory on JBoss).
Packaging your Seam app will require some thought - I am not familiar with Glassfish and what it provides, but let's imagine you're using Seam with JavaBeans POJO's for your actions and Hibernate 3 for your persistence (as I am); if you're app had this same structure, you would simply need to make sure that all the Hibernate 3 dependencies are packaged in your .war. (along with Seam jars and its dependencies, and any JSF dependencies you choose).
Seam is currently built against an older version of the EJB3 spec than what ships with Glassfish. This causes problems for Seam apps on Glassfish. You can follow this forum post:
or this JIRA
You would need to ask the JBoss EJB3 forums what their ETA is on a final release. Based on the latest forum chatter it sounds like support for Glassfish may slip until after the Seam 1.0 release at JBoss World.