The 3.7.0 release is being VOTE'd on at the moment on the dev@jena list:

https://lists.apache.org/thread.html/a5139d2c560b4b5ce161f8440d4a2cdb733e291f52f355593ef33e69@%3Cdev.jena.apache.org%3E

(being Easter, it might be slower than usual.)

which includes links to the proposed www.apache.org/dist/jena area and the artifacts to send to maven central.

The documentation is on http://jena.staging.apache.org/

As we use the maven release plugin, the version moves to the next one as the proposed release is built.

    Andy


On 02/04/18 08:03, Jean-Marc Vanel wrote:
Latest Jena source works fine with semantic_forms
<https://github.com/jmvanel/semantic_forms/wiki> application (uses Jena TDB
API with Lucene connection ).

According to latest commit, the Jena release is almost there :

*commit b850a9cd118db450becb1568f52a3e2617833e61 (HEAD -> master,
origin/master, origin/HEAD)*
*Author: Andy Seaborne <[email protected] <[email protected]>>*
*Date:   Thu Mar 29 17:08:34 2018 +0100*
*    [maven-release-plugin] prepare for next development iteration*

and jena version is already  "3.8.0-SNAPSHOT" .


2018-03-13 19:53 GMT+01:00 Andy Seaborne <[email protected]>:

The development community is heading towards Jena 3.7.0 (no specific date
- as ever, it has to fit around the volunteers time).

We'd like to encourage you to test it before the release using the
development code and builds. Drop over to dev@.


There is lots in this release, much more than listed here, but areas that
might be worth you investigating and testing include:


== Java9: Running on a Java9 platform is supported
Language requirement remain Java8.  More below.

== SPARQL: Evaluation change

JENA-1507: Changes to GROUP BY when the WHERE pattern has no results.

== Feature

JENA-1461: Allow ARQ custom functions to be written in JavaScript
Draft documentation:
http://jena.apache.org/documentation/query/javascript-functions.html

== API

This release is not binary compatible (NB Releases are not guaranteed to
be binary compatible nor mix-and-match versions of jars).
This time there are specific API changes:

JENA-1389: Return `this` rather than `void` from Dataset
JENA-1495: PR#368 "Return Model from PrefixMapping methods"


** Java9

Java8 is the current LTS version of Java and receives security updates.
The next LTS is Java11. [Sched]

[Sched] http://www.oracle.com/technetwork/java/eol-135779.html

There are different cases for running with Java9:

[1] Run on a Java9 JVM
[2] Build using Java9 JDK, output Java8 class files.
[3] Java9 required - language features and runtime library
[4] Java9 modules

[1] at Jena 3.7.0, running with a Java9 platform (except jena-elephas) is
supported.

[2] at Jena 3.7.0, running maven (3.5.0 or later) using Java9 to produce
Java8 bytecode is supported (except as noted).  We now run a Jenkins job
daily to check this for the main jars.

[3] The project has no current plans to require a Java9 language runtime.
The language requirement is still Java8.

[4] Jena jars can work as automatic modules but Jena itself does not
provide a "modules" version. Proper migration needs all the dependencies to
be modules, and also has implications on the upstream. Contribution and
discussions are welcome!

For discussion and background see

[A] http://blog.joda.org/2017/05/java-se-9-jpms-automatic-modules.html
[B] http://blog.joda.org/2017/04/java-se-9-jpms-module-naming.html

And note: Java 9 is obsolete March 2018, as soon as Java10 comes out.
http://openjdk.java.net/projects/jdk/10/#Schedule

Notes:

jena-elephas depends on Hadoop that depends on jdk.tools which is not
available in Java9.




Reply via email to