On Fri, Aug 10, 2012 at 10:31 AM, Andy Seaborne <a...@apache.org> wrote: > On 10/08/12 18:02, Stephen Allen wrote: >> >> I have dreams of replacing "org.openjena.atlas.lib.Closeable" with >> "java.lang.AutoCloseable" (or at least making it a subinterface)... > > > Juno does a lot of resource close checking so your dream may be reality > already, but in a different place.
I wanted AutoCloseable mostly for the try-with-resources (I'm tired of dealing with finally blocks and irrational scoping on closeable objects!) > When I have a moment, I want to fix on the codebase to be warning clean on > Juno (a couple need thinking about). But only one of my machines is > Juno-ised because Juno+Scala needs a special build of ScalaIDE so I got > patient. > > >> Does anyone have any thoughts on a timeline for a switch to Java 7? >> Do we wait until Jena 3? (Can't get to JIRA to see if it's mentioned >> there) > > > Generally (= pre ASF), Jena has supported the last two releases of Java. > EOL-isms only became relevant with Java 1.5. > > The uptake of Java7 isn't that stunning. > > This plan is Oracle's intention at the moment - in the recent past, sticking > to plans hasn't always come about so let's see what actually happens. > > Seems hard to make a solid project decision just at the moment > My view is that if people are upgrading their Jena dependency, then they should also be able to upgrade their Java version as well. Java 7 is pretty strongly compatible with Java 6 and seems to be available now on all platforms. But I agree, perhaps wait and see what Oracle does w/ the EOL. >> >> On Fri, Aug 10, 2012 at 3:38 AM, Andy Seaborne <a...@apache.org> wrote: >>> >>> http://www.theregister.co.uk/2012/08/09/java_se6_gets_second_extension/ >>> >>> EOL for Java6 is set to February 2013. >>> >>> Andy > >
