Public probably noticed that Shane Bryzak (Seam3 project lead) published blog about Seam.Next transformation. This is Seam team reaction to SoWhatsHappeningWithSeam blog responses.
While Seam core team is focusing on Seam.Next transformation I am still slowly progressing with Seam 2.3.0.Beta1. This is not changing!
So I would like to write about Seam 2.3.0 in development.
First of all JSF2 support, this is primary reason to do 2.3.0 release. Although it is late and still not fully finished, 2.3.0.Beta1 will be very soon on table. Right now you can try current 2.3.0-SNAPSHOT from JBoss snapshot Maven repository (https://repository.jboss.org/nexus/content/repositories/snapshots/) and report all issue you have with them.
Just use Seam maven artifacts in your project:
You can also see CI results on Jenkins which does deploying of snapshots to above mentioned repository.
I ask myself regularly if Seam community appreciates keeping old JSF 1.2 integration in Seam if there will be support of JSF 2 included. Could you help me with the answer?
Second target for 2.3.0 is a support of JBoss AS7 and enjoying speed and modularity of new JBoss AS 7 runtime. I think this is interesting also like JSF2 support, but it raises some tasks which weren't originally planned for 2.3.0 and hinders finishing of 2.3.0. It is connected with upgrade of Hibernate Core, Search and JBPM3 integration for top level view and also replacing of Seam integration testsuite which is based on very old JBoss Embedded beta3. I will defer some of that tasks to later beta2 or 2.4.
I hope that with regarding to all responses in forums, Seam community would like primary to have done JSF2 support and all other tasks are for now on other side of our/my focus. If you have different opinion(s), raise your hands and shout loudly ;-).