On 09/07/2020 17:42, Martynas Jusevičius wrote:
Any chance to squeeze JENA-1936 in? :)
No. This thread started in June.
There's work to be done even to identify what the problem and why it is
different to the BGP case (if it is).
Even if a PR were available (there isn't), if it touches anything deep
in Jena, then during the release cycle is not a good idea.
Andy
On Thu, 9 Jul 2020 at 17.55, Andy Seaborne <a...@apache.org> wrote:
First attempt failed - ran into the issue that source-release skips
files with the string "target" anywhere in the file name.
SHACL has "targets" so data in test files has the string in it and there
are new test files for the SHACLC reader.
Oops.
The temporary fix is to move the under src/test/resources but stil read
them as files (because URI resolution comes into play, I don't want to
classpath load the files).
Trying again.
Andy
On 08/07/2020 20:32, Andy Seaborne wrote:
I've started on producing the release.
On 30/06/2020 17:16, Andy Seaborne wrote:
3.15.0 has some problems for users - the fulljar Fuseki does not start
without modification, and the commands print error/warning message to
stdout. The logging issue is especially a nuisance for new people and
it has come up a few times on stackoverflow.
RDF* for TDB1 and TDB2 are now working.
There is a SHACL Compact Syntax reader.
https://s.apache.org/jena-3.16.0-jira
If that's OK with everyone, let's do 3.16.0 to have the latest version
being tidier.
PR #770 (a jena-text-es fix) should go in. - anything else outstanding?
Andy
-- Upgrades
JENA-1896 : Google Guava to 24.1-jre to 29-jre
----
Contrib:
JENA-1901
Provide default implementations for some of SecurityEvaluator's methods
Unassigned Pavel Mikhailovskii
JENA-1904 : QueryExecution.sparqlService fix.
Daniel Arturo Casals Amat
----
Features:
JENA-1921 : SHACLC reader
JENA-1899 : RDF* for TDB1, TDB2
Also:
JENA-1924 : Invalid IRIs
JENA-1918 : Performance improvements for paths
JENA-1913 : Fuseki: Support multiple "--file" arguments to load all
the files into one database.
