On Nov 12, 2008, at 9:10 AM, ant elder wrote:
Any opinions on having Java SE 6 be the default for the Tuscany 2.0
stream?
A benefit of doing this is that a lot of the basic dependencies we
use are included in Java SE 6 by default so we wouldn't need to
include all those dependencies separately so we'd look much smaller
and lightweight. Tuscany 2.0 would still work with Java SE 5 you'd
just need to include the extra dependencies manually which we'd need
to document how to do. So its weighing up if the extra burden and
complexity for those Java SE 5 users is out weighed by the smallness
for the Java SE 6 users. I think it could be worth doing.
There are definite advantages, in that regard.
FYI, Geronimo is having a similar discussion - http://apache.markmail.org/message/fskiwsxsb7vfbpnk
. One comment there is that "J2SE 5.0 is in its Java Technology End
of Life (EOL) transition period. The EOL transition period began
April 8th, 2008 and will complete October 30th, 2009, when J2SE 5.0
will have reached its End of Service Life (EOSL)"
Right. Personally, I don't think such an EOL statement should have a
lot of bearing on the decision. Important things are technical reasons
to move to Java 6 and opinions of users. Will note that there was some
reluctance to move to Java 6 in the geronimo community (including
mine). No conclusions, yet.
I'd assume that Java 6 is the default, not minimum java level. So,
then becomes a question of how Java 5 is supported/tolerated.
Assuming, there's a reasonable path for Java 5 users, I don't see much
of a downside.
--kevan
