On Wed, Jul 30, 2008 at 8:47 AM, Felix Knecht <[EMAIL PROTECTED]> wrote:
> > Then I think the solution is rather clear: we need to migrate to 1.5. If >> Sun is not supporting Java 1.4 then I don't want to support it as well in >> our _trunk_. >> >> People that need to stick to Java 1.4 still have a choice: We have >> released 2.2 that works with Java 1.4. >> >> Therefore I propose to switch to 1.5 and focus on getting real work done. >> >> But when switching the version why don't switch to 1.6 (I think it's on > MacOSX now also available). Otherwise we have to switch again in 1 year or > so (see http://java.sun.com/products/archive/eol.policy.html). EOL for 1.5 > is October 2009. > >> WDYT? >> >> > There might be people who can't run 1.6 yet. In particular we know some people are still stuck on old versions of Websphere and similar. We've had this discussion before and I'm on the side that we can't support legacy code forever. However, I do feel that a jump to 1.6 might be a bit premature. We just had this discussion internally over the last couple of weeks and we found several 1.6 incompatibilities forcing us to stay on 1.5 for the moment. If we do have a need to move to 1.6 in the future it shouldn't be that much of an issue to change at that point? -- Peter Hunsberger
