On 25/04/13 22:04, Lebling, David (US SSA) wrote:
Andy,
I'd love to be able to test SDB 1.3.6 but we are not able to update
to Jena 2.10.1 for reasons too tedious to go into here, and trying to
use this SDB with an older version of Jena (*cough* 2.7.3 *cough)
Cough and splutter.
doesn't seem to work, probably not to your surprise. The exact
exception is: "Caused by: java.lang.ClassNotFoundException:
org.apache.jena.atlas.lib.Lib". SDB 1.3.5 worked fine in that
environment, aside from the SDB "duplicate node" error I reported
earlier.
The ClassNotFound is just some internal reorganisation to improve the
modularity of the code base. That's why I'd prefer not to let SDB get
too out of sync with the main releases.
Was there a JIRA raised for the "duplicate node" error?
Andy
Dave Lebling
-----Original Message----- From: Andy Seaborne
[mailto:[email protected]] Sent: Thursday, April 25, 2013 3:51 PM To:
[email protected] Subject: Jena 2.10.1 / SDB 1.3.6 -- testing for
next release
We'd like to get testing reports on the current Jena development
build over the next few weeks for a release of Jena 2.10.1.
You can get a copy of the development build (via maven dependency or
a download):
http://jena.staging.apache.org/download/index.html#development-builds
There are two areas of special note: Turtle output and query
timeouts.
== Turtle output
The writer for Turtle which has been rewritten. The exact output
layout of the Turtle may change.
Full details of using the writing subsystem:
http://jena.staging.apache.org/documentation/io/rdf-output.html
== Query timeouts (including in Fuseki)
Timeouts were not firing in the right places so that often the
time-to-first-row was remaining and behaving as the
time-to-last-row. This is fixed - if you use query timeouts in Fuseki
you'll see a difference in behaviour if you had timeouts going off.
Also The status code from a timeouts query was incorrectly 408 - it's
now 503.
== SDB
At the same time, we'd like to do a separate, coordinated release of
SDB to align the libraries.
But we need help from SDB users in order to get proper testing of
SDB. Please test 1.3.6-SNAPSHOT
(if there aren't enough test reports, we'll have to then see whether
a release of SDB is a good idea or not)
Andy
