Given we only have about 5 weeks between now and when should cut a 2.2
branch, I'm not sure I'd waste time on this. As Jack pointed out in
another reply, Java SE 6 has been out almost 2 years, so its time to
move on.... If users want to stay on Java SE 5, we'll be glad to apply
fixes to the 2.1 branch.
-Donald
Joe Bohn wrote:
I'm certainly in favor of only performing certification on SE 6 runtime
for 2.2.
I wonder if it would be possible for us to include the JAXB and JAXWS
support in a plugin for users that might need to continue on SE 5. If
this isn't too difficult (or too much of a maintenance nightmare) then
we might consider it. Is that even possible?
Joe
Donald Woods wrote:
The time has come to make the hard decision -
Do we only build and certify Geronimo 2.2 on the Sun 1.6.0 JDK and
drop support for running on Java SE 5?
Pros:
- Reduce testing effort to one version of Java
- Allows us to use the JAXB 2.1, JAX-WS 2.1 and wsgen tools in the
JDK, instead of shipping those jars in our assemblies (and removes
some more Sun RI from our assemblies) :-)
- Keeps us current on the latest Java release
- All major platforms have a Java SE 6 solution:
- Sun provided 1.6.0 for Windows, Solaris, Linux on Intel/AMD
- MacOS 10.5.x provides 1.6.0_07
- openSUSE 11.0/11.1 users can install Sun 1.6.0_10 from build repos
- Ubuntu 7.04 and later users can install Sun 1.6.0 from net repos
- Fedora 9/10 comes with OpenJDK 6, but users can install Sun 1.6.0
- IBM provides 1.6.0 SR2 for AIX, pLinux, zLinux, zOS, ...
Cons:
- Users will have to upgrade to Java SE 6 to run Geronimo 2.2
- Will require us to maintain the 2.1 branch during 2009 for any users
who want to stay on Java SE 5
I'm for moving to a Java SE 6 only runtime for Geronimo 2.2.
-Donald
