seam-gen and JBoss Tools both set up the test environment properly for you. I suggest trying one of these.
I had not touched to seam-gen for a long time and gave it another spin. It seems like it has improvements as generated projects are more firendly to Netbeans.
I have a project started as a NetBeans Enterprise application and it has a complex set of build.xml files generated and maintained by Netbeans. My plan was patching it up with a test target.
I see that seam-gen's organization of files in a project is different. At this point I am willing to convert the whole thing into something standard (in relation with Seam) as I have gone through too many issues for months with %90 related with configuration and I spent a really annoying time on trying to keep the things run in concert rather than writing my application itself.
So in this case my question becomes if I start with a seam-gen generated template project, could I convert it to an app that is
1) POJO based rather than EJB
2) Uses Hibernate for the persistence rather than JPA
3) deployable to Glassfish
Or should I perhaps wait the GA version of RHDS and convert from Netbeans which would be somewhat challenging as I have no experience with Eclipse.
Would be great to hear your opinions
1) Yes, ootb seam-gen and generate-entities doesn't use EJB3s - only things like new-action do
2) Yes, a bit more work, but just remove all jpa annotations, remove persistence.xml, add hibernate.cfg.xml and .hbm.xml
3) Again, more work, but use the jee5 example as ref point to get the right config files/libs
We are working on app server guides for Seam, and glassfish is at the top of the list.