The Seam 2.x branch will be supported with EAP 6. You're certainly welcome to use that. It will include support for JSF 2 and JPA 2.
Seam 3 is community only and will not be offered as a supported offering in EAP 6. We're hoping to get more word out on this in the coming months (hopefully weeks). If you're looking for a supported framework you're comfortable with, look at Seam 2.3. Beta1 was recently released.
Jason. thanks for your prompt response.
The situation is summarize as follows:
The project is to develop a database of 400 tables aproxidamente, the duration is estimated for 2 years and 6 engineers.
Knowing the benefits of 'SEAM 3.1'. see it as the ideal tool. Because if done with version 2.3 and then migrate to 3.1, would be expensive and runs the risk of not achieving it in a timely fashion.
The concept applied is: should we wait for seam 3.1 and if so, we would have the same functionality of a style framework 2.3. to implement large projects?
Another, very viable option would be to look at MyFaces CODI and Apache DeltaSpike (Seam 3 and MyFaces CODI and some others). CDI on it's own because it's extensible is a very good choice. Because your project is a long project you could help us identify places we need to fill gaps, fix bugs, etc.
For the same functionality, it really depends on which features you're looking at.
1. Error. with seam 2.3 beta1
Using seam-gen sources from: E:\javajdk\jboss-seam-2.3.0.B1\seam-gen
E:\javajdk\jboss-seam-2.3.0.B1\seam-gen\build.xml:42: Cannot find E:\javajdk\jboss-seam-2.3.0.B1/build/common.build.xml imported from E:\javajdk\jboss-seam-2.3.0.B1\seam-gen\build.xml
Total time: 0 seconds
2. Seam 3 and MyFaces CODI and some others).
I find functional projects: with creating entity bean, session and view, reverse engineering, etc.