On Fri, 2015-05-29 at 18:08 +0300, Robert Munteanu wrote: > > On May 29, 2015 5:55 PM, "Daniel Klco" <[email protected]> wrote: > > > > Considering that Oracle is already stopped public updates for both > Java 6 > > and that the Premium Support ends December 2015, it would seem to > make > > sense to standardize on Java 7 for new development and change > everything > > over at the end of the year. > That would be nice. However, there's also IBM and HP and they don't > follow the same support policies as Oracle. > Robert
I removed support for sling.java.version = 5 and made 6 the default. https://issues.apache.org/jira/browse/SLING-4772 Robert > > > > Either way this shakes out, we should create a Java support > schedule to > > make sure it's clear to users and contributors what versions are > supported, > > default and end of life across the Sling Launchpad versions. > > > > -Dan > > > > On Fri, May 29, 2015 at 5:31 AM, Carsten Ziegeler < > [email protected]> > > wrote: > > > > > Am 29.05.15 um 11:23 schrieb Stefan Seifert: > > > > it's just that we cannot use features like Closeable when we > still > > > support JDK 1.6. > > > > > > Yepp, that's why I said, if it makes sense for a bundle to be > based on > > > 1.7 then we're free to do it. > > > > > > > > > > > if we do not want switch to JDK 1.7 now perhaps we should come > up with a > > > plan/roadmap when > > > > to do the switch and document it on the website, then it is > possible > > > for upstream projects to take this into account. > > > > > > The launchpad already requires Java 7, and everything runs on > Java 7. > > > It's just that we should not blindly update everything to depend > on 7 > > > > > > Regards > > > Carsten > > > -- > > > Carsten Ziegeler > > > Adobe Research Switzerland > > > [email protected] > > >
