3.0.0 Milestone 2

We're pleased to announce the second milestone build for rdf4j 3.0.0.

Use 3.0.0-M2 as your version in maven to test it out.

As well what's new since the first milestone release (https://github.com/eclipse/rdf4j/releases/tag/3.0.0-M1) we now have:

• various bug fixes
• support for sh:not in the ShaclSail
• faster Models.isomorphic(....) support

rdf4j 2.5.3

Rdf4j 2.5.3 is a patch release containing several bug fixes, including:

• custom HTTP header handling in HTTPRepository
• handling of queries with COUNT in the LuceneSail
• performance of context id retrieval in native store
• handling of FROM/FROM NAMED clauses in SparqlBuilder

For a full overview of issues, see:

https://github.com/eclipse/rdf4j/milestone/37?closed=1

3.0.0 Milestone 1

We're pleased to announce the first milestone build for rdf4j 3.0.0.

Rdf4j 3.0 is a major new release of the rdf4j framework. It contains several backward incompatible changes.

Some highlights:

• Major improvements to the SHACL Sail
• Cleanup of core APIs (removing deprecated and obsolete code)
• Preparing rdf4j for Java 11/12 compatibility
• Rdf4j Server / Workbench upgrade to Servlet API 3.1

This first milestone build is not yet feature-complete:

• issues fixed in 3.0 milestone 1
• issues planned for 3.0 release

Upgrade notes

Rdf4j 3.0 contains several backward incompatible changes. We distinguish changes that affect users of the Rdf4j tools (Console, Workbench, Server), changes that affect users of the Rdf4j APIs and libraries, and changes that affect third party Sail / Repository implementations. See the linked issues for further details.

rdf4j tools users

• Due to an up upgrade to Spring 5.1. Rdf4j Server and Rdf4j Workbench now require a servlet container that support Servlet API 3.1. For Apache Tomcat, that means Tomcat 8 or better. For Eclipse Jetty, it means Jetty 9 or better.
• The RDFS inferencer has changed its default behavior for inferred triples.

rdf4j API/library users

• The deprecated Graph API has been removed. Any code that still uses Graph, GraphImpl, or GraphUtil will need to be rewritten to use corresponding features in the Model API.
• Deprecated methods have been removed from the Model API. Any existing code that uses the deprecated methods will need to be rewritten to use the recommend new methods.
• The deprecated package org.eclipse.rdf4j.model.util.language has been removed.

third-party sail / repository implementors

• invoking init() (or initialize()) on a Repository or Sail object is no longer mandatory.
• we allow injection of optimizers into a Sail object.
• testsuites and compliance tests have been moved and refactored. If you were depending on a particular testsuite and can no longer find it, contact us.

Rdf4j 2.5.2

Rdf4j 2.5.2 is a patch release containing several bug fixes:

• Performance of statement removal in NativeStore significantly improved
• Rio parser IRI processing performance improved
• Several SPARQL bug fixes

For a full overview of issues, see:

https://github.com/eclipse/rdf4j/milestone/36?closed=1

RD4FJ 2.5.1

RDF4J 2.5.1 is a patch release containing bug fixes and a library update, including:

• Updated Jackson to 2.9.8
• SPARQL in Console: fix for NPE and for namespace prefixes
• SparqlBuilder: was missing in BOM, and file: not recognized as protocol
• Use buffered streams in some test

For a list of bug fixes, see:

https://github.com/eclipse/rdf4j/milestone/35?closed=1

RDF4J 2.5.0

RDF4J 2.5.0 is a minor release that addresses over 70 issues, and includes several major new features and improvements, including:

• A host of major improvements to the SHACL support, including more streamlined initialization, and major extension of the range of SHACL features supported;
• Several improvements to the RDF4J Console, including commands to show and edit namespaces;
• Replacement of the old RDFS inferencer with a new, faster Schema-caching RDFS inferencer;
• Improvements and bug fixes in the SparqlBuilder

For a full overview of all improvements, and bug fixes see:

• (https://github.com/eclipse/rdf4j/milestone/26?closed=1

RDF4J 2.4.6

RDF4J 2.4.6 is patch release containing one fix:

• fix for duplicated children in JSON-LD hierarchical view

See also:

• https://github.com/eclipse/rdf4j/milestone/34?closed=1

RDF4J 2.5.0 Milestone 2

This is the second milestone build for the upcoming 2.5.0 release, which will include:

• Improved and extended SHACL support
• Diagnostics support for SHACL execution
• More streamlined SHACL API support
• More efficient RDFS reasoning by means of the SchemaCachingInference
• Various improvements and new features in the RDF4J Console
• Support for parser configuration via runtime system properties.

For a list of changes see:

• https://github.com/eclipse/rdf4j/milestone/26?closed=1

RDF4J 2.4.5

RDF4J 2.4.5 is patch release including 2 bug fixes:

• fix for NativeStore file system leak: make sure that the transaction cache files actually get deleted on MS-Windows
• fix calculation of hash functions in SPARQL: always use UTF8 (as per specification), instead of the platform’s default charset

For a list of bug fixes, see:

• https://github.com/eclipse/rdf4j/milestone/33?closed=1

RDF4J 2.4.4

Release 2.4.4 is a patch release covering bug fixes and a workaround for an OpenJDK 8 ScheduledThreadPoolExecutor bug:

• fix for a NPE on transaction UPDATE with wrong MIME type
• fix for SPARQL function SECONDS() to also return fractions of seconds
• fix for memory leak in remote transactions

Workaround for JDK-8129861: high processor load.
Setting the property -Dorg.eclipse.rdf4j.client.executors.jdkbug will use 1 core thread (instead of 0) for clients, to avoid a 100% CPU load even when doing nothing.

For a list of changes see:

• https://github.com/eclipse/rdf4j/milestone/32?closed=1