On 29/04/14 20:29, Stephen Allen wrote:
One simple change I would really like to make when we switch to Java 7 is
to make org.apache.jena.atlas.lib.Closeable extend java.lang.AutoCloseable.
That way we can take advantage of try-with-resources.
Which classes/patterns in particular did you want autoclosability?
org.apache.jena.atlas.lib.Closeable gets used widely.
oaj.lib.Closeable defines close without a checked exception;
java.lang.AutoCloseable defines close to throw an exception:
Andy
-Stephen
On Tue, Apr 29, 2014 at 12:55 PM, Andy Seaborne <[email protected]> wrote:
Zhe,
By setting the java level, we're setting
1/ what level of JVM is assumed at runtime
2/ what level of language is assumed
3/ what runtime library operations are assumed available
not specific features within those conformance criteria. We'd judge
contributions on those criteria.
Andy
(if there is a tool that would go round and converted all unnecessary
generics to <>, I'd run it on the code I habitually see!)
On 29/04/14 16:38, Alan Wu wrote:
Hi,
I am wondering what JDK7 specific features Jena is planning to use?
Thanks,
Zhe
On 4/29/2014 4:10 AM, Andy Seaborne wrote:
+1
Andy
On 29/04/14 09:36, Rob Vesse wrote:
Hi All
This is a vote on whether to drop Java 6 support in future Jena releases
since Java 6 has officially
The Jena team is planning to make a final Java 6 supporting release
as our
next release (2.11.2) and then all subsequent releases will be Java 7
(2.12.0 onwards)
Everyone in the community is welcome to vote, if you have an
objection to
this decision please explain why dropping Java 6 support would cause you
problems
Please vote to approve this change:
[ ] +1 Approve dropping of Java 6 support after the next release
[ ] 0 Don't care
[ ] -1 Keep Java 6 support, because ...
This vote will be open to the end of
Friday, 2nd May 2014, 23:59 UTC
(72 hours from the same hour tonight UTC).
Thanks,
Rob
