If we set Java 6 as the minimum for all modules, this creates unnecessary work to ship a bugfix or enhancements to users running on Java 5. And we have a lot of them. The difference between Java 5 and Java 6 in terms of the languange or the libraries is not that huge, so I think there is rarely a need to really require Java 6 for a module. If it does, it's fine - but if not we should not disable it from running in existing installations per default
Carsten 2013/1/31 Justin Edelson <[email protected]>: > -0 > > Why even try to support Java 5? Let's just say Java 6 as a minimum across > the board and be done with it. > > > > On Thu, Jan 31, 2013 at 11:47 AM, Carsten Ziegeler > <[email protected]>wrote: > >> Hi, >> >> we see more and more problems with supporting Java 5 and we discussed >> this several times in the past year(s?). So let's finally call a vote >> and see where we all are. >> >> I propose to drop Java 5 support in general - we should try to stick >> to it where possible for supporting existing installations, but each >> module should be free to set the base to Java 6 if it makes sense. >> >> We should also mark the bundles which require Java 6 (I think Felix >> proposed a way for this some time ago). >> >> Please cast your votes :) >> >> Regards >> Carsten >> -- >> Carsten Ziegeler >> [email protected] >> -- Carsten Ziegeler [email protected]
