On the money Arbi :-)
There aren't significant improvements *that we need as maintainers of Seam* in Java 6
- and certainly not ones that justify increasing the barriers to adoption. We aren't a
container, we need to run in as many places as possible.
JBoss AS 6 is a container, and has much more control over where it runs. It will require
Java 6.
On 13 Apr 2010, at 16:10, Arbi Sookazian wrote:
You have a point but there are many shops out there (believe it or
not) that are running JVM 1.4 (I worked at one recently). They do not have the
time/money/resources/needs to upgrade. For Seam apps, 1.5 minimum is obviously required.
This is most likely about supporting as many customers/users as possible. Our current
Seam/EE5 project is running JVM 1.5. Thank god for annotations, varargs and generics,
etc.
On the other hand, it would be nice to "force" shops to upgrade their JRE/JDK
to 1.6 as a pre-requisite for JBoss 6...
On Tue, Apr 13, 2010 at 7:34 AM, Shervin Asgari <shervin.asgari(a)redpill-linpro.com>
wrote:
Forgot to cc list
Pete Muir wrote:
Just to remind everyone (not sure if this is a problem or not atm ;-) but all Seam
modules should be developed using Java 5 unless there is a strong reason to use Java 6. We
should used the Hudson jobs to ensure that the code builds with Java 5.
_______________________________________________
seam-dev mailing list
seam-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/seam-dev
Why? Java 5 is end of life and not any longer supported.
Shervin
_______________________________________________
seam-dev mailing list
seam-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/seam-dev
_______________________________________________
seam-dev mailing list
seam-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/seam-dev