Assuming we switch, what should be the best practice to support upstream dependencies on Java 6 (like AEM 6.1) when doing eg hotfix releases? Afaics so far Sling did not adopt making branches for these cases.
Cheers, Stefan On 5/28/15 6:12 PM, "Stefan Seifert" <[email protected]> wrote: >why not drop Java 6 support for new released bundles at all? > >+1 for using Java 7 as default and minimum Java version. > >stefan > >>-----Original Message----- >>From: Robert Munteanu [mailto:[email protected]] >>Sent: Thursday, May 28, 2015 11:58 AM >>To: [email protected] >>Subject: Moving to Java 7 ( was: Make ResourceResolver implement >>Closeable) >> >>This might've been buried under the 'Closeable' thread so resending so >>that it does not suprise anyone. >> >>Currently our projects can use either Java 5 or 6, with 5 being the >>default. This is very much out of date and we're missing out on >>language improvements. I would suggest changing the supported Java >>versions from >> >>- 5 (default), 6 >>- 6, 7 (default) >> >>I would have preferred >> >>- 6, 7 (default), 8 >> >>But Java 8 support is blocked due to SLING-4702 [1]. >> >>Thoughts on the proposed change for the supported Java versions? >> >>Cheers, >> >>Robert >> >>[1]: https://issues.apache.org/jira/browse/SLING-4702 >> >>On Tue, 2015-05-26 at 16:38 +0200, Carsten Ziegeler wrote: >>> Am 26.05.15 um 16:14 schrieb Robert Munteanu: >>> > Hi Roy, >>> > >>> > On Tue, 2015-05-26 at 15:51 +0200, Roy Teeuwen wrote: >>> > > Hello, >>> > > >>> > > As of Java 7, it is possible by implementing the Closeable or >>> > > AutoCloseable to use the try-with-resources statement. This makes >>> > > the >>> > > notation a lot shorter than the try-finally block. Is there a >>> > > reason >>> > > that the ResourceResolver does not implement the Closeable >>> > > interface, >>> > > and would it be possible to let it implement it? >>> > >>> > We should "just" move to Java 7 by default. >>> > >>> +1 >>> >>> Carsten >>> >>> >
