You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@jena.apache.org by Andy Seaborne <an...@apache.org> on 2016/05/04 19:53:03 UTC

[VOTE] Release Jena 3.1.0 (2nd proposed candidate)

Hi,

Here is a vote on a release of Jena 3.1.0
(with Fuseki 2.4.0 and Fuseki 1.4.0).

This is the second proposed candidate for this release.

This fixes, from the previous proposed candidate
1/ Presence of binaries in the source-release
2/ Jump in large size of binary downloads due to javadoc inclusion

* Dependency changes:

Upgrades:
   jsonld-java : 2.8.2
   jackson 2.6.3
   slf4j 1.7.20
   dexx collections 0.6

Key features listed below.

Everyone, not just committers, is invited to test and vote.

Staging repository:
https://repository.apache.org/content/repositories/orgapachejena-1012/

Proposed dist/ area:
     https://dist.apache.org/repos/dist/dev/jena/

Keys:
     https://svn.apache.org/repos/asf/jena/dist/KEYS

Git commit (browser URL):
     http://git-wip-us.apache.org/repos/asf/jena/commit/e7ee6bb6

Git Commit Hash:
     e7ee6bb69a5d7ce930a2529dd576a9ea209596a3

Git Commit Tag:
     jena-3.1.0-rc3

Please vote to approve this release:

     [ ] +1 Approve the release
     [ ]  0 Don't care
     [ ] -1 Don't release, because ...

This vote will be open to at least

      7th May 2016, 23:59 UTC

If you expect to check the release but the 72 hour limit does not work 
for you, please email within the schedule above with an expected time 
and we can extend the vote period.

Thanks,

     Andy

Checking needed:

+ does everything work on Linux?
+ does everything work on MS Windows?
+ does everything work on OS X?
+ are the GPG signatures fine?
+ are the checksums correct?
+ is there a source archive?
+ can the source archive really be built?
+ is there a correct LICENSE and NOTICE file in each artifact
       (both source and binary artifacts)?
+ does the NOTICE file contain all necessary attributions?
+ have any licenses of dependencies changed due to upgrades?
        if so have LICENSE and NOTICE been upgraded appropriately?
+ does the tag/commit in the SCM contain reproducible sources?


---------------------------

Key features of the release:

* In-memory txn dataset (Adam Soroka) (RC in 3.0.1)

http://jena.staging.apache.org/documentation/rdf/datasets.html

* Quads (Qihong Lin) (RC in 3.0.1)

http://jena.staging.apache.org/documentation/query/construct-quad.html

* DatasetGraphs & transactions integration

* Alternative QueryParsers in jena-text

* new module jena-cmds
"jena.*"

* Fuseki: Multiple service per file, shared datasets

* Logging
log4j marked <optional>

* New custom functions and aggregate functions
Added:
* afn:springf (contribution from Alessandro Seganti)
* The XQuery/XPath Functions and Operators "math:" functions
* Custom aggregates for stdev etc. (also STDEV etc as keywords).

* FactoryRDF
Parsing RDF now saves space by interning RDFTerms created
during a each parser run.

* OSGi fixes (Jaroslav Pullmann)

* General maintenance: about 80 JIRA.

Re: [VOTE] Release Jena 3.1.0 (2nd proposed candidate)

Posted by Osma Suominen <os...@helsinki.fi>.

+1

I couldn't do any thorough testing within this timeframe (yesterday was 
a public holiday, tomorrow is a Saturday), but I've been running recent 
snapshot versions of both Fuseki1 and Fuseki2 on various testing and 
development machines. Today I updated one dev server to this rc2 
version, without any issues.

-Osma

On 04/05/16 22:53, Andy Seaborne wrote:
> Hi,
>
> Here is a vote on a release of Jena 3.1.0
> (with Fuseki 2.4.0 and Fuseki 1.4.0).
>
> This is the second proposed candidate for this release.
>
> This fixes, from the previous proposed candidate
> 1/ Presence of binaries in the source-release
> 2/ Jump in large size of binary downloads due to javadoc inclusion
>
> * Dependency changes:
>
> Upgrades:
>    jsonld-java : 2.8.2
>    jackson 2.6.3
>    slf4j 1.7.20
>    dexx collections 0.6
>
> Key features listed below.
>
> Everyone, not just committers, is invited to test and vote.
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachejena-1012/
>
> Proposed dist/ area:
>      https://dist.apache.org/repos/dist/dev/jena/
>
> Keys:
>      https://svn.apache.org/repos/asf/jena/dist/KEYS
>
> Git commit (browser URL):
>      http://git-wip-us.apache.org/repos/asf/jena/commit/e7ee6bb6
>
> Git Commit Hash:
>      e7ee6bb69a5d7ce930a2529dd576a9ea209596a3
>
> Git Commit Tag:
>      jena-3.1.0-rc3
>
> Please vote to approve this release:
>
>      [ ] +1 Approve the release
>      [ ]  0 Don't care
>      [ ] -1 Don't release, because ...
>
> This vote will be open to at least
>
>       7th May 2016, 23:59 UTC
>
> If you expect to check the release but the 72 hour limit does not work
> for you, please email within the schedule above with an expected time
> and we can extend the vote period.
>
> Thanks,
>
>      Andy
>
> Checking needed:
>
> + does everything work on Linux?
> + does everything work on MS Windows?
> + does everything work on OS X?
> + are the GPG signatures fine?
> + are the checksums correct?
> + is there a source archive?
> + can the source archive really be built?
> + is there a correct LICENSE and NOTICE file in each artifact
>        (both source and binary artifacts)?
> + does the NOTICE file contain all necessary attributions?
> + have any licenses of dependencies changed due to upgrades?
>         if so have LICENSE and NOTICE been upgraded appropriately?
> + does the tag/commit in the SCM contain reproducible sources?
>
>
> ---------------------------
>
> Key features of the release:
>
> * In-memory txn dataset (Adam Soroka) (RC in 3.0.1)
>
> http://jena.staging.apache.org/documentation/rdf/datasets.html
>
> * Quads (Qihong Lin) (RC in 3.0.1)
>
> http://jena.staging.apache.org/documentation/query/construct-quad.html
>
> * DatasetGraphs & transactions integration
>
> * Alternative QueryParsers in jena-text
>
> * new module jena-cmds
> "jena.*"
>
> * Fuseki: Multiple service per file, shared datasets
>
> * Logging
> log4j marked <optional>
>
> * New custom functions and aggregate functions
> Added:
> * afn:springf (contribution from Alessandro Seganti)
> * The XQuery/XPath Functions and Operators "math:" functions
> * Custom aggregates for stdev etc. (also STDEV etc as keywords).
>
> * FactoryRDF
> Parsing RDF now saves space by interning RDFTerms created
> during a each parser run.
>
> * OSGi fixes (Jaroslav Pullmann)
>
> * General maintenance: about 80 JIRA.
>


-- 
Osma Suominen
D.Sc. (Tech), Information Systems Specialist
National Library of Finland
P.O. Box 26 (Kaikukatu 4)
00014 HELSINGIN YLIOPISTO
Tel. +358 50 3199529
osma.suominen@helsinki.fi
http://www.nationallibrary.fi

3.1.0 status Was : [] Release Jena 3.1.0 (2nd proposed candidate)

Posted by Andy Seaborne <an...@apache.org>.

The current status is that we have

3 +1 binding
1 -1 non-binding

I am concerned about the expectations here.

Osma very kindly tested the build in his environment which I think is 
above-and-beyond the requirements for voting. Thank you, Osma.

The release was signalled 18 April.
Dev builds happen every day.

If testing only starts on a release candidate and not development 
builds, and that testing is coupled to gating the release, we not going 
to make progress.

Like any system, we release with JIRA that are open. So create new JIRA 
and consider the overall context. Making certain new issues gating 
criteria on a release when normally they would be JIRA items is making 
them too important.

Are users and downstream integrators helped or hindered by delay?

We can end up either with repeated release attempts or need to 
separately release different modules or having formal RC releases, the 
last two mean more votes and more Release Manager time.

At this point, I will offer to be Release Manager for a 3.1.1 release in 
1-2 months time (if anything gets fixed) but blocking 3.1.0 now on 
previously unreported issues is blocking all the other good things in 3.1.0.

Release early, release often.

    Andy

PS
It takes a long time (elapsed) to sort out OSGi issues. We now have 
competing views of OSGi usage.

An option is to release 3.1.0 without an OSGi bundle, just the source code.

On 04/05/16 20:53, Andy Seaborne wrote:
> Hi,
>
> Here is a vote on a release of Jena 3.1.0
> (with Fuseki 2.4.0 and Fuseki 1.4.0).
>
> This is the second proposed candidate for this release.
>
> This fixes, from the previous proposed candidate
> 1/ Presence of binaries in the source-release
> 2/ Jump in large size of binary downloads due to javadoc inclusion
>
> * Dependency changes:
>
> Upgrades:
>    jsonld-java : 2.8.2
>    jackson 2.6.3
>    slf4j 1.7.20
>    dexx collections 0.6
>
> Key features listed below.
>
> Everyone, not just committers, is invited to test and vote.
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachejena-1012/
>
> Proposed dist/ area:
>      https://dist.apache.org/repos/dist/dev/jena/
>
> Keys:
>      https://svn.apache.org/repos/asf/jena/dist/KEYS
>
> Git commit (browser URL):
>      http://git-wip-us.apache.org/repos/asf/jena/commit/e7ee6bb6
>
> Git Commit Hash:
>      e7ee6bb69a5d7ce930a2529dd576a9ea209596a3
>
> Git Commit Tag:
>      jena-3.1.0-rc3
>
> Please vote to approve this release:
>
>      [ ] +1 Approve the release
>      [ ]  0 Don't care
>      [ ] -1 Don't release, because ...
>
> This vote will be open to at least
>
>       7th May 2016, 23:59 UTC
>
> If you expect to check the release but the 72 hour limit does not work
> for you, please email within the schedule above with an expected time
> and we can extend the vote period.
>
> Thanks,
>
>      Andy
>
> Checking needed:
>
> + does everything work on Linux?
> + does everything work on MS Windows?
> + does everything work on OS X?
> + are the GPG signatures fine?
> + are the checksums correct?
> + is there a source archive?
> + can the source archive really be built?
> + is there a correct LICENSE and NOTICE file in each artifact
>        (both source and binary artifacts)?
> + does the NOTICE file contain all necessary attributions?
> + have any licenses of dependencies changed due to upgrades?
>         if so have LICENSE and NOTICE been upgraded appropriately?
> + does the tag/commit in the SCM contain reproducible sources?
>
>
> ---------------------------
>
> Key features of the release:
>
> * In-memory txn dataset (Adam Soroka) (RC in 3.0.1)
>
> http://jena.staging.apache.org/documentation/rdf/datasets.html
>
> * Quads (Qihong Lin) (RC in 3.0.1)
>
> http://jena.staging.apache.org/documentation/query/construct-quad.html
>
> * DatasetGraphs & transactions integration
>
> * Alternative QueryParsers in jena-text
>
> * new module jena-cmds
> "jena.*"
>
> * Fuseki: Multiple service per file, shared datasets
>
> * Logging
> log4j marked <optional>
>
> * New custom functions and aggregate functions
> Added:
> * afn:springf (contribution from Alessandro Seganti)
> * The XQuery/XPath Functions and Operators "math:" functions
> * Custom aggregates for stdev etc. (also STDEV etc as keywords).
>
> * FactoryRDF
> Parsing RDF now saves space by interning RDFTerms created
> during a each parser run.
>
> * OSGi fixes (Jaroslav Pullmann)
>
> * General maintenance: about 80 JIRA.
>

Re: [VOTE] Release Jena 3.1.0 (2nd proposed candidate)

Posted by Andy Seaborne <an...@apache.org>.

+1

	Andy

On 04/05/16 20:53, Andy Seaborne wrote:
> Hi,
>
> Here is a vote on a release of Jena 3.1.0
> (with Fuseki 2.4.0 and Fuseki 1.4.0).
>
> This is the second proposed candidate for this release.
>
> This fixes, from the previous proposed candidate
> 1/ Presence of binaries in the source-release
> 2/ Jump in large size of binary downloads due to javadoc inclusion
>
> * Dependency changes:
>
> Upgrades:
>    jsonld-java : 2.8.2
>    jackson 2.6.3
>    slf4j 1.7.20
>    dexx collections 0.6
>
> Key features listed below.
>
> Everyone, not just committers, is invited to test and vote.
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachejena-1012/
>
> Proposed dist/ area:
>      https://dist.apache.org/repos/dist/dev/jena/
>
> Keys:
>      https://svn.apache.org/repos/asf/jena/dist/KEYS
>
> Git commit (browser URL):
>      http://git-wip-us.apache.org/repos/asf/jena/commit/e7ee6bb6
>
> Git Commit Hash:
>      e7ee6bb69a5d7ce930a2529dd576a9ea209596a3
>
> Git Commit Tag:
>      jena-3.1.0-rc3
>
> Please vote to approve this release:
>
>      [ ] +1 Approve the release
>      [ ]  0 Don't care
>      [ ] -1 Don't release, because ...
>
> This vote will be open to at least
>
>       7th May 2016, 23:59 UTC
>
> If you expect to check the release but the 72 hour limit does not work
> for you, please email within the schedule above with an expected time
> and we can extend the vote period.
>
> Thanks,
>
>      Andy
>
> Checking needed:
>
> + does everything work on Linux?
> + does everything work on MS Windows?
> + does everything work on OS X?
> + are the GPG signatures fine?
> + are the checksums correct?
> + is there a source archive?
> + can the source archive really be built?
> + is there a correct LICENSE and NOTICE file in each artifact
>        (both source and binary artifacts)?
> + does the NOTICE file contain all necessary attributions?
> + have any licenses of dependencies changed due to upgrades?
>         if so have LICENSE and NOTICE been upgraded appropriately?
> + does the tag/commit in the SCM contain reproducible sources?
>
>
> ---------------------------
>
> Key features of the release:
>
> * In-memory txn dataset (Adam Soroka) (RC in 3.0.1)
>
> http://jena.staging.apache.org/documentation/rdf/datasets.html
>
> * Quads (Qihong Lin) (RC in 3.0.1)
>
> http://jena.staging.apache.org/documentation/query/construct-quad.html
>
> * DatasetGraphs & transactions integration
>
> * Alternative QueryParsers in jena-text
>
> * new module jena-cmds
> "jena.*"
>
> * Fuseki: Multiple service per file, shared datasets
>
> * Logging
> log4j marked <optional>
>
> * New custom functions and aggregate functions
> Added:
> * afn:springf (contribution from Alessandro Seganti)
> * The XQuery/XPath Functions and Operators "math:" functions
> * Custom aggregates for stdev etc. (also STDEV etc as keywords).
>
> * FactoryRDF
> Parsing RDF now saves space by interning RDFTerms created
> during a each parser run.
>
> * OSGi fixes (Jaroslav Pullmann)
>
> * General maintenance: about 80 JIRA.
>

Re: [] Release Jena 3.1.0 (2nd proposed candidate)

Posted by Andy Seaborne <an...@apache.org>.

On 11/05/16 17:27, A. Soroka wrote:
> Andy-- sorry, I accidentally left in "--thread 2.0C" when I shouldn't have. I did get the errors with it, but I also got them without it, just "mvn -Dmaven.repo.local=/tmp/maven clean install". I just tried it again, no threading trickiness, starting from an empty Maven repo, and got the same problems, and the run finished up with dozens of gigs free on disc.
>
> Maybe someone else who uses a Mac can try this? It's so weird and I've never seen it before. I really suspect that it's something odd about me and not Jena. {grin} But I thought I should report it.

Reports are good!

	Thanks
	Andy



> ---
> A. Soroka
> The University of Virginia Library
>
>> On May 11, 2016, at 12:14 PM, Andy Seaborne <an...@apache.org> wrote:
>>
>> As far as I know, nothing has changed in the area of jena-jdbc and you've got through TDB testing to get to jena-jdbc.
>>
>> Did it ever work at any version? Especially with/without "--threads 2.0C"
>>
>> I just tried "--thread 2.0C" with an empty repo and got weird things happening. maven 3.3.3 fell apart.
>>
>> (e.g. "Failed to install project artifacts: MavenProject: org.apache.jena:jena-text:3.1.1-SNAPSHOT:: Artifact is not fully assembled") see below.
>>
>> "--threads 2" worked.
>>
>> (I have a quad core, hyper threaded CPU)
>>
>> Lots of things happen out of order so if disk is shared between tests things will go wrong.
>>
>>
>> There are two kinds of exceptions:
>>
>> case 1:
>>
>> java.lang.Exception: Unexpected exception
>>
>> expected<java.sql.SQLFeatureNotSupportedException> but was<org.apache.jena.tdb.base.file.FileException>
>>
>> case 2:
>>
>> org.apache.jena.tdb.base.file.FileException: BlockMgrMapped.segmentAllocate: Segment = 0
>>
>>
>> What's the disk setup?
>> (have you run out of disk space? Macs report at least all the space for sparse files, maybe they use that space)
>>
>> If a file area is shared in some way, parallel might mess up.
>>
>>     Andy
>>
>> "--thread 2.0C" ==>
>> [INFO] ------------------------------------------------------------------------
>> [INFO] Reactor Summary:
>> [INFO]
>>
>> (edited to fit)
>>
>> Parent ............................... SUCCESS [  1.284 s]
>> Shadowed external libraries .......... SUCCESS [  2.187 s]
>> IRI .................................. SUCCESS [  4.612 s]
>> Base Common Environment .............. SUCCESS [  7.816 s]
>> Core ................................. SUCCESS [ 35.050 s]
>> ARQ (SPARQL 1.1 Query Engine) ........ SUCCESS [ 38.207 s]
>> TDB (Native Triple Store) ............ SUCCESS [01:01 min]
>> Libraries POM ........................ SUCCESS [  0.185 s]
>> Command line tools ................... SUCCESS [ 18.849 s]
>> SPARQL Text Search ................... SKIPPED
>> SPARQL Spatial Search ................ SKIPPED
>> Data Tables for RDF and SPARQL ....... SUCCESS [  6.451 s]
>> SDB (SQL based triple store) ......... SKIPPED
>> Fuseki1 .............................. SKIPPED
>> Fuseki - A SPARQL 1.1 Server ......... SUCCESS [  0.183 s]
>> Fuseki Server Engine ................. SKIPPED
>> Fuseki WAR File ...................... SKIPPED
>> Fuseki Server Standalone Jar ......... SKIPPED
>> Fuseki Binary Distribution ........... SKIPPED
>> Security Permissions ................. SUCCESS [ 18.584 s]
>> JDBC Parent .......................... SUCCESS [  0.732 s]
>> JDBC Core API ........................ SUCCESS [ 34.060 s]
>> JDBC Remote Endpoint Driver .......... SKIPPED
>> JDBC In-Memory Driver ................ SUCCESS [ 12.506 s]
>> JDBC TDB Driver ...................... SKIPPED
>> JDBC Driver Bundle ................... SKIPPED
>> Maven Plugins, including schemagen ... FAILURE [ 10.110 s]
>> Elephas .............................. SUCCESS [  0.422 s]
>> Elephas - Common API ................. SUCCESS [  3.943 s]
>> Elephas - I/O ........................ SKIPPED
>> Elephas - Map/Reduce ................. SUCCESS [ 18.601 s]
>> Elephas - Statistics Demo App ........ SKIPPED
>> Distribution ......................... SUCCESS [  7.141 s]
>> OSGi ................................. SUCCESS [  0.291 s]
>> OSGi bundle .......................... SUCCESS [ 13.043 s]
>> OSGi Karaf features .................. SUCCESS [  0.892 s]
>> Extras ............................... SUCCESS [  0.301 s]
>> Extras - Query Builder ............... SUCCESS [ 14.210 s]
>> [INFO] Apache Jena ........................................ SUCCESS [ 0.948 s]
>>
>> On 11/05/16 16:14, A. Soroka wrote:
>>> For Mac OS X, using
>>>
>>> wget --no-check-certificate https://dist.apache.org/repos/dist/dev/jena/source/jena-3.1.0-source-release.zip
>>> unzip jena-3.1.0-source-release.zip
>>> cd jena-3.1.0
>>> mvn --threads 2.0C -Dmaven.repo.local=/tmp/maven clean install
>>>
>>> I got errors (not failures) in jena-jdbc-driver-tdb, specifically for TestTdbDiskResultSets. I've put it up here:
>>>
>>> https://gist.github.com/ajs6f/fded4a65dba235f3ad614c7f89444d99
>>>
>>> Lots and lots of org.apache.jena.tdb.base.file.FileExceptions. Does that look like a real problem or just something weird about my setup?
>>>
>>> ---
>>> A. Soroka
>>> The University of Virginia Library
>>>
>>>> On May 9, 2016, at 8:56 AM, Andy Seaborne <an...@apache.org> wrote:
>>>>
>>>> On 09/05/16 13:44, Stian Soiland-Reyes wrote:
>>>>>> OSGi didn't work at 3.0.1 either as I understand PR#134
>>>>> No, 3.0.1 jena-osgi was also broken because of the ServiceLoader issue.
>>>>>
>>>>
>>>> That's what I meant - jena-osgi did not work whatever the reason.
>>>>
>>>> As it took so long to show up, we can conclude the usage of the project-produced OSGi bundle is low.
>>>>
>>>>> Due to the Karaf issue you mention, then I suggest adding
>>>>> org.apache.servicemix.bundles.xerces as an
>>>>> informational <optional>true</optional> dependency.
>>>>>
>>>>> See https://github.com/apache/jena/pull/140
>>>>
>>>> Great - I hope OSGi users will test that out.
>>>>
>>>> 	Andy
>>>>
>>>
>>
>

Re: [] Release Jena 3.1.0 (2nd proposed candidate)

Posted by "A. Soroka" <aj...@virginia.edu>.

Andy-- sorry, I accidentally left in "--thread 2.0C" when I shouldn't have. I did get the errors with it, but I also got them without it, just "mvn -Dmaven.repo.local=/tmp/maven clean install". I just tried it again, no threading trickiness, starting from an empty Maven repo, and got the same problems, and the run finished up with dozens of gigs free on disc.

Maybe someone else who uses a Mac can try this? It's so weird and I've never seen it before. I really suspect that it's something odd about me and not Jena. {grin} But I thought I should report it.

---
A. Soroka
The University of Virginia Library

> On May 11, 2016, at 12:14 PM, Andy Seaborne <an...@apache.org> wrote:
> 
> As far as I know, nothing has changed in the area of jena-jdbc and you've got through TDB testing to get to jena-jdbc.
> 
> Did it ever work at any version? Especially with/without "--threads 2.0C"
> 
> I just tried "--thread 2.0C" with an empty repo and got weird things happening. maven 3.3.3 fell apart.
> 
> (e.g. "Failed to install project artifacts: MavenProject: org.apache.jena:jena-text:3.1.1-SNAPSHOT:: Artifact is not fully assembled") see below.
> 
> "--threads 2" worked.
> 
> (I have a quad core, hyper threaded CPU)
> 
> Lots of things happen out of order so if disk is shared between tests things will go wrong.
> 
> 
> There are two kinds of exceptions:
> 
> case 1:
> 
> java.lang.Exception: Unexpected exception
> 
> expected<java.sql.SQLFeatureNotSupportedException> but was<org.apache.jena.tdb.base.file.FileException>
> 
> case 2:
> 
> org.apache.jena.tdb.base.file.FileException: BlockMgrMapped.segmentAllocate: Segment = 0
> 
> 
> What's the disk setup?
> (have you run out of disk space? Macs report at least all the space for sparse files, maybe they use that space)
> 
> If a file area is shared in some way, parallel might mess up.
> 
>    Andy
> 
> "--thread 2.0C" ==>
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> 
> (edited to fit)
> 
> Parent ............................... SUCCESS [  1.284 s]
> Shadowed external libraries .......... SUCCESS [  2.187 s]
> IRI .................................. SUCCESS [  4.612 s]
> Base Common Environment .............. SUCCESS [  7.816 s]
> Core ................................. SUCCESS [ 35.050 s]
> ARQ (SPARQL 1.1 Query Engine) ........ SUCCESS [ 38.207 s]
> TDB (Native Triple Store) ............ SUCCESS [01:01 min]
> Libraries POM ........................ SUCCESS [  0.185 s]
> Command line tools ................... SUCCESS [ 18.849 s]
> SPARQL Text Search ................... SKIPPED
> SPARQL Spatial Search ................ SKIPPED
> Data Tables for RDF and SPARQL ....... SUCCESS [  6.451 s]
> SDB (SQL based triple store) ......... SKIPPED
> Fuseki1 .............................. SKIPPED
> Fuseki - A SPARQL 1.1 Server ......... SUCCESS [  0.183 s]
> Fuseki Server Engine ................. SKIPPED
> Fuseki WAR File ...................... SKIPPED
> Fuseki Server Standalone Jar ......... SKIPPED
> Fuseki Binary Distribution ........... SKIPPED
> Security Permissions ................. SUCCESS [ 18.584 s]
> JDBC Parent .......................... SUCCESS [  0.732 s]
> JDBC Core API ........................ SUCCESS [ 34.060 s]
> JDBC Remote Endpoint Driver .......... SKIPPED
> JDBC In-Memory Driver ................ SUCCESS [ 12.506 s]
> JDBC TDB Driver ...................... SKIPPED
> JDBC Driver Bundle ................... SKIPPED
> Maven Plugins, including schemagen ... FAILURE [ 10.110 s]
> Elephas .............................. SUCCESS [  0.422 s]
> Elephas - Common API ................. SUCCESS [  3.943 s]
> Elephas - I/O ........................ SKIPPED
> Elephas - Map/Reduce ................. SUCCESS [ 18.601 s]
> Elephas - Statistics Demo App ........ SKIPPED
> Distribution ......................... SUCCESS [  7.141 s]
> OSGi ................................. SUCCESS [  0.291 s]
> OSGi bundle .......................... SUCCESS [ 13.043 s]
> OSGi Karaf features .................. SUCCESS [  0.892 s]
> Extras ............................... SUCCESS [  0.301 s]
> Extras - Query Builder ............... SUCCESS [ 14.210 s]
> [INFO] Apache Jena ........................................ SUCCESS [ 0.948 s]
> 
> On 11/05/16 16:14, A. Soroka wrote:
>> For Mac OS X, using
>> 
>> wget --no-check-certificate https://dist.apache.org/repos/dist/dev/jena/source/jena-3.1.0-source-release.zip
>> unzip jena-3.1.0-source-release.zip
>> cd jena-3.1.0
>> mvn --threads 2.0C -Dmaven.repo.local=/tmp/maven clean install
>> 
>> I got errors (not failures) in jena-jdbc-driver-tdb, specifically for TestTdbDiskResultSets. I've put it up here:
>> 
>> https://gist.github.com/ajs6f/fded4a65dba235f3ad614c7f89444d99
>> 
>> Lots and lots of org.apache.jena.tdb.base.file.FileExceptions. Does that look like a real problem or just something weird about my setup?
>> 
>> ---
>> A. Soroka
>> The University of Virginia Library
>> 
>>> On May 9, 2016, at 8:56 AM, Andy Seaborne <an...@apache.org> wrote:
>>> 
>>> On 09/05/16 13:44, Stian Soiland-Reyes wrote:
>>>>> OSGi didn't work at 3.0.1 either as I understand PR#134
>>>> No, 3.0.1 jena-osgi was also broken because of the ServiceLoader issue.
>>>> 
>>> 
>>> That's what I meant - jena-osgi did not work whatever the reason.
>>> 
>>> As it took so long to show up, we can conclude the usage of the project-produced OSGi bundle is low.
>>> 
>>>> Due to the Karaf issue you mention, then I suggest adding
>>>> org.apache.servicemix.bundles.xerces as an
>>>> informational <optional>true</optional> dependency.
>>>> 
>>>> See https://github.com/apache/jena/pull/140
>>> 
>>> Great - I hope OSGi users will test that out.
>>> 
>>> 	Andy
>>> 
>> 
>

Re: [] Release Jena 3.1.0 (2nd proposed candidate)

Posted by Andy Seaborne <an...@apache.org>.

As far as I know, nothing has changed in the area of jena-jdbc and 
you've got through TDB testing to get to jena-jdbc.

Did it ever work at any version? Especially with/without "--threads 2.0C"

I just tried "--thread 2.0C" with an empty repo and got weird things 
happening. maven 3.3.3 fell apart.

(e.g. "Failed to install project artifacts: MavenProject: 
org.apache.jena:jena-text:3.1.1-SNAPSHOT:: Artifact is not fully 
assembled") see below.

"--threads 2" worked.

(I have a quad core, hyper threaded CPU)

Lots of things happen out of order so if disk is shared between tests 
things will go wrong.


There are two kinds of exceptions:

case 1:

java.lang.Exception: Unexpected exception

expected<java.sql.SQLFeatureNotSupportedException> but 
was<org.apache.jena.tdb.base.file.FileException>

case 2:

org.apache.jena.tdb.base.file.FileException: 
BlockMgrMapped.segmentAllocate: Segment = 0


What's the disk setup?
(have you run out of disk space? Macs report at least all the space for 
sparse files, maybe they use that space)

If a file area is shared in some way, parallel might mess up.

     Andy

"--thread 2.0C" ==>
[INFO] 
------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]

(edited to fit)

  Parent ............................... SUCCESS [  1.284 s]
  Shadowed external libraries .......... SUCCESS [  2.187 s]
  IRI .................................. SUCCESS [  4.612 s]
  Base Common Environment .............. SUCCESS [  7.816 s]
  Core ................................. SUCCESS [ 35.050 s]
  ARQ (SPARQL 1.1 Query Engine) ........ SUCCESS [ 38.207 s]
  TDB (Native Triple Store) ............ SUCCESS [01:01 min]
  Libraries POM ........................ SUCCESS [  0.185 s]
  Command line tools ................... SUCCESS [ 18.849 s]
  SPARQL Text Search ................... SKIPPED
  SPARQL Spatial Search ................ SKIPPED
  Data Tables for RDF and SPARQL ....... SUCCESS [  6.451 s]
  SDB (SQL based triple store) ......... SKIPPED
  Fuseki1 .............................. SKIPPED
  Fuseki - A SPARQL 1.1 Server ......... SUCCESS [  0.183 s]
  Fuseki Server Engine ................. SKIPPED
  Fuseki WAR File ...................... SKIPPED
  Fuseki Server Standalone Jar ......... SKIPPED
  Fuseki Binary Distribution ........... SKIPPED
  Security Permissions ................. SUCCESS [ 18.584 s]
  JDBC Parent .......................... SUCCESS [  0.732 s]
  JDBC Core API ........................ SUCCESS [ 34.060 s]
  JDBC Remote Endpoint Driver .......... SKIPPED
  JDBC In-Memory Driver ................ SUCCESS [ 12.506 s]
  JDBC TDB Driver ...................... SKIPPED
  JDBC Driver Bundle ................... SKIPPED
  Maven Plugins, including schemagen ... FAILURE [ 10.110 s]
  Elephas .............................. SUCCESS [  0.422 s]
  Elephas - Common API ................. SUCCESS [  3.943 s]
  Elephas - I/O ........................ SKIPPED
  Elephas - Map/Reduce ................. SUCCESS [ 18.601 s]
  Elephas - Statistics Demo App ........ SKIPPED
  Distribution ......................... SUCCESS [  7.141 s]
  OSGi ................................. SUCCESS [  0.291 s]
  OSGi bundle .......................... SUCCESS [ 13.043 s]
  OSGi Karaf features .................. SUCCESS [  0.892 s]
  Extras ............................... SUCCESS [  0.301 s]
  Extras - Query Builder ............... SUCCESS [ 14.210 s]
[INFO] Apache Jena ........................................ SUCCESS [ 
0.948 s]

On 11/05/16 16:14, A. Soroka wrote:
> For Mac OS X, using
>
> wget --no-check-certificate https://dist.apache.org/repos/dist/dev/jena/source/jena-3.1.0-source-release.zip
> unzip jena-3.1.0-source-release.zip
> cd jena-3.1.0
> mvn --threads 2.0C -Dmaven.repo.local=/tmp/maven clean install
>
> I got errors (not failures) in jena-jdbc-driver-tdb, specifically for TestTdbDiskResultSets. I've put it up here:
>
> https://gist.github.com/ajs6f/fded4a65dba235f3ad614c7f89444d99
>
> Lots and lots of org.apache.jena.tdb.base.file.FileExceptions. Does that look like a real problem or just something weird about my setup?
>
> ---
> A. Soroka
> The University of Virginia Library
>
>> On May 9, 2016, at 8:56 AM, Andy Seaborne <an...@apache.org> wrote:
>>
>> On 09/05/16 13:44, Stian Soiland-Reyes wrote:
>>>> OSGi didn't work at 3.0.1 either as I understand PR#134
>>> No, 3.0.1 jena-osgi was also broken because of the ServiceLoader issue.
>>>
>>
>> That's what I meant - jena-osgi did not work whatever the reason.
>>
>> As it took so long to show up, we can conclude the usage of the project-produced OSGi bundle is low.
>>
>>> Due to the Karaf issue you mention, then I suggest adding
>>> org.apache.servicemix.bundles.xerces as an
>>> informational <optional>true</optional> dependency.
>>>
>>> See https://github.com/apache/jena/pull/140
>>
>> Great - I hope OSGi users will test that out.
>>
>> 	Andy
>>
>

Re: [] Release Jena 3.1.0 (2nd proposed candidate)

Posted by "A. Soroka" <aj...@virginia.edu>.

For Mac OS X, using

wget --no-check-certificate https://dist.apache.org/repos/dist/dev/jena/source/jena-3.1.0-source-release.zip
unzip jena-3.1.0-source-release.zip
cd jena-3.1.0
mvn --threads 2.0C -Dmaven.repo.local=/tmp/maven clean install

I got errors (not failures) in jena-jdbc-driver-tdb, specifically for TestTdbDiskResultSets. I've put it up here:

https://gist.github.com/ajs6f/fded4a65dba235f3ad614c7f89444d99

Lots and lots of org.apache.jena.tdb.base.file.FileExceptions. Does that look like a real problem or just something weird about my setup?

---
A. Soroka
The University of Virginia Library

> On May 9, 2016, at 8:56 AM, Andy Seaborne <an...@apache.org> wrote:
> 
> On 09/05/16 13:44, Stian Soiland-Reyes wrote:
>>> OSGi didn't work at 3.0.1 either as I understand PR#134
>> No, 3.0.1 jena-osgi was also broken because of the ServiceLoader issue.
>> 
> 
> That's what I meant - jena-osgi did not work whatever the reason.
> 
> As it took so long to show up, we can conclude the usage of the project-produced OSGi bundle is low.
> 
>> Due to the Karaf issue you mention, then I suggest adding
>> org.apache.servicemix.bundles.xerces as an
>> informational <optional>true</optional> dependency.
>> 
>> See https://github.com/apache/jena/pull/140
> 
> Great - I hope OSGi users will test that out.
> 
> 	Andy
>

Re: [] Release Jena 3.1.0 (2nd proposed candidate)

Posted by Andy Seaborne <an...@apache.org>.

On 09/05/16 13:44, Stian Soiland-Reyes wrote:
>> OSGi didn't work at 3.0.1 either as I understand PR#134
> No, 3.0.1 jena-osgi was also broken because of the ServiceLoader issue.
>

That's what I meant - jena-osgi did not work whatever the reason.

As it took so long to show up, we can conclude the usage of the 
project-produced OSGi bundle is low.

> Due to the Karaf issue you mention, then I suggest adding
> org.apache.servicemix.bundles.xerces as an
> informational <optional>true</optional> dependency.
>
> See https://github.com/apache/jena/pull/140

Great - I hope OSGi users will test that out.

	Andy

Re: [] Release Jena 3.1.0 (2nd proposed candidate)

Posted by Stian Soiland-Reyes <st...@apache.org>.

On 9 May 2016 at 12:54, Andy Seaborne <an...@apache.org> wrote:
>> BTW -
>> http://central.maven.org/maven2/xerces/xercesImpl/2.8.1/xercesImpl-2.8.1.jar
>
> Jena does not use 2.8.1. The dependency is on 2.11.0.

Sorry, I picked the wrong 'latest' one by not sorting numerically in
my head.. :)

Official xerces 2.11.0 is neither an OSGi bundle.

> The jena-osgi-test module does run, even though it is still broken for use
> in the build.

> OSGi didn't work at 3.0.1 either as I understand PR#134

No, 3.0.1 jena-osgi was also broken because of the ServiceLoader issue.

> https://github.com/apache/jena/pull/134#issuecomment-209474708
> seems to discuss the Xerces issue.

Due to the Karaf issue you mention, then I suggest adding
org.apache.servicemix.bundles.xerces as an
informational <optional>true</optional> dependency.

See https://github.com/apache/jena/pull/140

-- 
Stian Soiland-Reyes
Apache Taverna (incubating), Apache Commons RDF (incubating)
http://orcid.org/0000-0001-9842-9718

Re: [] Release Jena 3.1.0 (2nd proposed candidate)

Posted by Andy Seaborne <an...@apache.org>.

 > BTW - 
http://central.maven.org/maven2/xerces/xercesImpl/2.8.1/xercesImpl-2.8.1.jar

Jena does not use 2.8.1. The dependency is on 2.11.0.

The jena-osgi-test module does run, even though it is still broken for 
use in the build.

OSGi didn't work at 3.0.1 either as I understand PR#134

https://github.com/apache/jena/pull/134#issuecomment-209474708

seems to discuss the Xerces issue.

	Andy

On 09/05/16 11:36, Stian Soiland-Reyes wrote:
> -1 I'm afraid.
>
> jena-osgi is missing (inclusion or dependency on) org/apache/xerces/util/XMLChar
>
> which means I can no longer compile with jena-osgi as a Maven <dependency>.
>
> Tested on http://github.com/apache/incubator-taverna-language/
>
> Running org.apache.taverna.robundle.validator.ValidatorTest
> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
> SLF4J: Defaulting to no-operation (NOP) logger implementation
> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for
> further details.
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.161
> sec <<< FAILURE! - in
> org.apache.taverna.robundle.validator.ValidatorTest
> test(org.apache.taverna.robundle.validator.ValidatorTest)  Time
> elapsed: 0.16 sec  <<< ERROR!
> java.lang.NoClassDefFoundError: org/apache/xerces/util/XMLChar
>      at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
>      at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
>      at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
>      at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
>      at org.apache.jena.rdf.model.impl.Util.notNameChar(Util.java:119)
>      at org.apache.jena.rdf.model.impl.Util.splitNamespaceXML(Util.java:77)
>      at org.apache.jena.graph.Node_URI.getLocalName(Node_URI.java:80)
>      at org.apache.jena.rdf.model.impl.ResourceImpl.getLocalName(ResourceImpl.java:152)
>      at org.apache.jena.rdf.model.impl.PropertyImpl.checkLocalName(PropertyImpl.java:64)
>      at org.apache.jena.rdf.model.impl.PropertyImpl.<init>(PropertyImpl.java:72)
>      at org.apache.jena.rdf.model.ResourceFactory$Impl.createProperty(ResourceFactory.java:335)
>      at org.apache.jena.rdf.model.ResourceFactory.createProperty(ResourceFactory.java:180)
>      at org.apache.jena.vocabulary.RDF.property(RDF.java:51)
>      at org.apache.jena.vocabulary.RDF.<clinit>(RDF.java:64)
>      at org.apache.jena.system.InitJenaCore.init(InitJenaCore.java:57)
>      at org.apache.jena.system.InitJenaCore.start(InitJenaCore.java:31)
>      at org.apache.jena.system.JenaSystem.lambda$init$1(JenaSystem.java:111)
>      at java.util.ArrayList.forEach(ArrayList.java:1249)
>      at org.apache.jena.system.JenaSystem.forEach(JenaSystem.java:186)
>      at org.apache.jena.system.JenaSystem.forEach(JenaSystem.java:163)
>      at org.apache.jena.system.JenaSystem.init(JenaSystem.java:109)
>      at org.apache.jena.rdf.model.ModelFactory.<clinit>(ModelFactory.java:49)
>      at org.apache.taverna.robundle.manifest.RDFToManifest.loadOntologyFromClasspath(RDFToManifest.java:315)
>      at org.apache.taverna.robundle.manifest.RDFToManifest.loadDCT(RDFToManifest.java:262)
>      at org.apache.taverna.robundle.manifest.RDFToManifest.loadOntologies(RDFToManifest.java:304)
>      at org.apache.taverna.robundle.manifest.RDFToManifest.<init>(RDFToManifest.java:182)
>      at org.apache.taverna.robundle.Bundle.readOrPopulateManifest(Bundle.java:114)
>      at org.apache.taverna.robundle.Bundle.getManifest(Bundle.java:87)
>      at org.apache.taverna.robundle.validator.RoValidator.validate(RoValidator.java:97)
>      at org.apache.taverna.robundle.validator.RoValidator.<init>(RoValidator.java:80)
>      at org.apache.taverna.robundle.validator.ValidatorTest.test(ValidatorTest.java:40)
>
> subsequent calls then fail with
>
> java.lang.NoClassDefFoundError: Could not initialize class
> org.apache.jena.rdf.model.ModelFactory
>
>
> I think this relates to Jaroslav' OSGi fixes - which I see now excludes xerces:
> https://github.com/apache/jena/blob/master/apache-jena-osgi/jena-osgi/pom.xml#L242
>
> this is fine - but if I'm to import Xerces I need to have a Maven
> dependency on a Bundle that provides it or make sure it's part of the
> boot delegation of my framework.
>
> This change is not noted in the release note - I would be OK with the
> change if the required workaround was described or the Maven POM for
> jena-osgi had the appropriate <dependency>.
>
>
>
> BTW - http://central.maven.org/maven2/xerces/xercesImpl/2.8.1/xercesImpl-2.8.1.jar
> is not an OSGi bundle - and Jena depends on org.apache.xerces.impl.dv
> which would not normally be exposed form a xerces bundle -
>
> Adding
>
> <dependency>
>      <groupId>org.apache.servicemix.bundles</groupId>
>      <artifactId>org.apache.servicemix.bundles.xerces</artifactId>
>      <version>2.11.0_1</version>
> </dependency>
>
> seems to work, though. Perhaps this could be added to jena-osgi/pom.xml ?
>
>
> I get another JSON-LD error with using the @context
> https://w3id.org/bundle/context that I need to check further what is
> the cause of that (it works fine with JSON-LD Playground).
>
> org.apache.jena.riot.RiotException: loading remote context failed:
> https://w3id.org/bundle/context
>      at org.apache.jena.riot.system.ErrorHandlerFactory$ErrorHandlerStd.error(ErrorHandlerFactory.java:128)
>      at org.apache.jena.riot.lang.JsonLDReader.read$(JsonLDReader.java:146)
>      at org.apache.jena.riot.lang.JsonLDReader.read(JsonLDReader.java:83)
>      at org.apache.jena.riot.RDFDataMgr.process(RDFDataMgr.java:861)
>      at org.apache.jena.riot.RDFDataMgr.read(RDFDataMgr.java:259)
>      at org.apache.jena.riot.RDFDataMgr.read(RDFDataMgr.java:245)
>
> On 4 May 2016 at 20:53, Andy Seaborne <an...@apache.org> wrote:
>> Hi,
>>
>> Here is a vote on a release of Jena 3.1.0
>> (with Fuseki 2.4.0 and Fuseki 1.4.0).
>>
>> This is the second proposed candidate for this release.
>>
>> This fixes, from the previous proposed candidate
>> 1/ Presence of binaries in the source-release
>> 2/ Jump in large size of binary downloads due to javadoc inclusion
>>
>> * Dependency changes:
>>
>> Upgrades:
>>    jsonld-java : 2.8.2
>>    jackson 2.6.3
>>    slf4j 1.7.20
>>    dexx collections 0.6
>>
>> Key features listed below.
>>
>> Everyone, not just committers, is invited to test and vote.
>>
>> Staging repository:
>> https://repository.apache.org/content/repositories/orgapachejena-1012/
>>
>> Proposed dist/ area:
>>      https://dist.apache.org/repos/dist/dev/jena/
>>
>> Keys:
>>      https://svn.apache.org/repos/asf/jena/dist/KEYS
>>
>> Git commit (browser URL):
>>      http://git-wip-us.apache.org/repos/asf/jena/commit/e7ee6bb6
>>
>> Git Commit Hash:
>>      e7ee6bb69a5d7ce930a2529dd576a9ea209596a3
>>
>> Git Commit Tag:
>>      jena-3.1.0-rc3
>>
>> Please vote to approve this release:
>>
>>      [ ] +1 Approve the release
>>      [ ]  0 Don't care
>>      [ ] -1 Don't release, because ...
>>
>> This vote will be open to at least
>>
>>       7th May 2016, 23:59 UTC
>>
>> If you expect to check the release but the 72 hour limit does not work for
>> you, please email within the schedule above with an expected time and we can
>> extend the vote period.
>>
>> Thanks,
>>
>>      Andy
>>
>> Checking needed:
>>
>> + does everything work on Linux?
>> + does everything work on MS Windows?
>> + does everything work on OS X?
>> + are the GPG signatures fine?
>> + are the checksums correct?
>> + is there a source archive?
>> + can the source archive really be built?
>> + is there a correct LICENSE and NOTICE file in each artifact
>>        (both source and binary artifacts)?
>> + does the NOTICE file contain all necessary attributions?
>> + have any licenses of dependencies changed due to upgrades?
>>         if so have LICENSE and NOTICE been upgraded appropriately?
>> + does the tag/commit in the SCM contain reproducible sources?
>>
>>
>> ---------------------------
>>
>> Key features of the release:
>>
>> * In-memory txn dataset (Adam Soroka) (RC in 3.0.1)
>>
>> http://jena.staging.apache.org/documentation/rdf/datasets.html
>>
>> * Quads (Qihong Lin) (RC in 3.0.1)
>>
>> http://jena.staging.apache.org/documentation/query/construct-quad.html
>>
>> * DatasetGraphs & transactions integration
>>
>> * Alternative QueryParsers in jena-text
>>
>> * new module jena-cmds
>> "jena.*"
>>
>> * Fuseki: Multiple service per file, shared datasets
>>
>> * Logging
>> log4j marked <optional>
>>
>> * New custom functions and aggregate functions
>> Added:
>> * afn:springf (contribution from Alessandro Seganti)
>> * The XQuery/XPath Functions and Operators "math:" functions
>> * Custom aggregates for stdev etc. (also STDEV etc as keywords).
>>
>> * FactoryRDF
>> Parsing RDF now saves space by interning RDFTerms created
>> during a each parser run.
>>
>> * OSGi fixes (Jaroslav Pullmann)
>>
>> * General maintenance: about 80 JIRA.
>>
>
>
>

Re: [VOTE] Release Jena 3.1.0 (2nd proposed candidate)

Posted by Stian Soiland-Reyes <st...@apache.org>.

Raised as https://issues.apache.org/jira/browse/JENA-1176

On 9 May 2016 at 13:33, Stian Soiland-Reyes <st...@apache.org> wrote:
> Yes, this error affects riot as well:
>
> stain@biggie:~/Downloads/apache-jena-3.1.0$ bin/riot --syntax=jsonld
> {"@context": "https://w3id.org/bundle/context",
>  "id": "http://example.com/fred",
>  "aggregates": "http://example.com/other"
> }
>
> Exception in thread "main" java.lang.NoSuchMethodError:
> org.apache.http.impl.client.cache.CacheConfig.custom()Lorg/apache/http/impl/client/cache/CacheConfig$Builder;
>     at com.github.jsonldjava.utils.JsonUtils.createDefaultHttpClient(JsonUtils.java:333)
>     at com.github.jsonldjava.utils.JsonUtils.getDefaultHttpClient(JsonUtils.java:323)
>     at com.github.jsonldjava.core.DocumentLoader.getHttpClient(DocumentLoader.java:84)
>     at com.github.jsonldjava.core.DocumentLoader.fromURL(DocumentLoader.java:59)
>     at com.github.jsonldjava.core.DocumentLoader.loadDocument(DocumentLoader.java:29)
>     at com.github.jsonldjava.core.Context.parse(Context.java:169)
>     at com.github.jsonldjava.core.Context.parse(Context.java:252)
>     at com.github.jsonldjava.core.JsonLdApi.expand(JsonLdApi.java:534)
>     at com.github.jsonldjava.core.JsonLdApi.expand(JsonLdApi.java:981)
>     at com.github.jsonldjava.core.JsonLdProcessor.expand(JsonLdProcessor.java:146)
>     at com.github.jsonldjava.core.JsonLdProcessor.toRDF(JsonLdProcessor.java:482)
>     at org.apache.jena.riot.lang.JsonLDReader.read$(JsonLDReader.java:143)
>     at org.apache.jena.riot.lang.JsonLDReader.read(JsonLDReader.java:83)
>     at riotcmd.CmdLangParse.parseRIOT(CmdLangParse.java:286)
>     at riotcmd.CmdLangParse.parseFile(CmdLangParse.java:202)
>     at riotcmd.CmdLangParse.parseFile(CmdLangParse.java:184)
>     at riotcmd.CmdLangParse.exec$(CmdLangParse.java:158)
>     at riotcmd.CmdLangParse.exec(CmdLangParse.java:132)
>     at jena.cmd.CmdMain.mainMethod(CmdMain.java:93)
>     at jena.cmd.CmdMain.mainRun(CmdMain.java:58)
>     at jena.cmd.CmdMain.mainRun(CmdMain.java:45)
>     at riotcmd.riot.main(riot.java:34)
>
> On 9 May 2016 at 12:16, François-Paul Servant
> <fr...@gmail.com> wrote:
>> Hi,
>>
>>> I get another JSON-LD error with using the @context
>>> https://w3id.org/bundle/context that I need to check further what is
>>> the cause of that (it works fine with JSON-LD Playground).
>>>
>>> org.apache.jena.riot.RiotException: loading remote context failed:
>>> https://w3id.org/bundle/context
>>>    at org.apache.jena.riot.system.ErrorHandlerFactory$ErrorHandlerStd.error(ErrorHandlerFactory.java:128)
>>>    at org.apache.jena.riot.lang.JsonLDReader.read$(JsonLDReader.java:146)
>>>    at org.apache.jena.riot.lang.JsonLDReader.read(JsonLDReader.java:83)
>>>    at org.apache.jena.riot.RDFDataMgr.process(RDFDataMgr.java:861)
>>>    at org.apache.jena.riot.RDFDataMgr.read(RDFDataMgr.java:259)
>>>    at org.apache.jena.riot.RDFDataMgr.read(RDFDataMgr.java:245)
>>>
>>
>> I don’t know whether it is the same thing, but I noticed (working with 3.1.1-SNAPSHOT) that following test, that attempts to read a simple jsonld document with an external context
>>
>> public class TestJsonLDReader {
>>
>>         @Test public final void test() {
>>                 String jsonld = "{\"@id\":\"_:b0\",\"@type\":\"http://schema.org/Person\",\"name\":\"John Doe\",\"@context\":\"http://schema.org/\"}";
>>                 StringReader reader = new StringReader(jsonld);
>>                 Model m = ModelFactory.createDefaultModel();
>>                 m.read(reader, null, "JSON-LD");
>>                 m.write(System.out, "TURTLE");
>>         }
>>
>> }
>>
>> gives:
>>
>> java.lang.NoSuchMethodError: org.apache.http.impl.client.cache.CacheConfig.custom()Lorg/apache/http/impl/client/cache/CacheConfig$Builder;
>>         at com.github.jsonldjava.utils.JsonUtils.createDefaultHttpClient(JsonUtils.java:333)
>>         at com.github.jsonldjava.utils.JsonUtils.getDefaultHttpClient(JsonUtils.java:323)
>>         at com.github.jsonldjava.core.DocumentLoader.getHttpClient(DocumentLoader.java:84)
>>         at com.github.jsonldjava.core.DocumentLoader.fromURL(DocumentLoader.java:59)
>>         at com.github.jsonldjava.core.DocumentLoader.loadDocument(DocumentLoader.java:29)
>>         at com.github.jsonldjava.core.Context.parse(Context.java:169)
>>         at com.github.jsonldjava.core.Context.parse(Context.java:252)
>>         at com.github.jsonldjava.core.JsonLdApi.expand(JsonLdApi.java:534)
>>         at com.github.jsonldjava.core.JsonLdApi.expand(JsonLdApi.java:981)
>>         at com.github.jsonldjava.core.JsonLdProcessor.expand(JsonLdProcessor.java:146)
>>         at com.github.jsonldjava.core.JsonLdProcessor.toRDF(JsonLdProcessor.java:482)
>>         at org.apache.jena.riot.lang.JsonLDReader.read$(JsonLDReader.java:143)
>>         at org.apache.jena.riot.lang.JsonLDReader.read(JsonLDReader.java:64)
>>
>> It seems that there is a conflict between the version of http-client cache used by JSON-LD java 0.8.2 (4.5.1), and the one that wants jena (4.2.6). Jena seems to really want to choose its version, cf pom/xml:
>>
>> +       /*
>> +      <dependency>
>> +        <groupId>com.github.jsonld-java</groupId>
>> +        <artifactId>jsonld-java</artifactId>
>> +        <version>${ver.jsonldjava}</version>
>> +        <exclusions>
>> +          <exclusion>
>> +            <groupId>commons-logging</groupId>
>> +            <artifactId>commons-logging</artifactId>
>> +          </exclusion>
>> +          <!-- Exclude so we use our choice of versions -->
>> +          <exclusion>
>> +            <groupId>org.apache.httpcomponents</groupId>
>> +            <artifactId>httpclient-cache</artifactId>
>> +          </exclusion>
>> +          <exclusion>
>> +            <groupId>org.apache.httpcomponents</groupId>
>> +            <artifactId>httpclient</artifactId>
>> +          </exclusion>
>>
>> Best,
>>
>> fps
>>
>
>
>
> --
> Stian Soiland-Reyes
> Apache Taverna (incubating), Apache Commons RDF (incubating)
> http://orcid.org/0000-0001-9842-9718



-- 
Stian Soiland-Reyes
Apache Taverna (incubating), Apache Commons RDF (incubating)
http://orcid.org/0000-0001-9842-9718

Re: [VOTE] Release Jena 3.1.0 (2nd proposed candidate)

Posted by Stian Soiland-Reyes <st...@apache.org>.

Yes, this error affects riot as well:

stain@biggie:~/Downloads/apache-jena-3.1.0$ bin/riot --syntax=jsonld
{"@context": "https://w3id.org/bundle/context",
 "id": "http://example.com/fred",
 "aggregates": "http://example.com/other"
}

Exception in thread "main" java.lang.NoSuchMethodError:
org.apache.http.impl.client.cache.CacheConfig.custom()Lorg/apache/http/impl/client/cache/CacheConfig$Builder;
    at com.github.jsonldjava.utils.JsonUtils.createDefaultHttpClient(JsonUtils.java:333)
    at com.github.jsonldjava.utils.JsonUtils.getDefaultHttpClient(JsonUtils.java:323)
    at com.github.jsonldjava.core.DocumentLoader.getHttpClient(DocumentLoader.java:84)
    at com.github.jsonldjava.core.DocumentLoader.fromURL(DocumentLoader.java:59)
    at com.github.jsonldjava.core.DocumentLoader.loadDocument(DocumentLoader.java:29)
    at com.github.jsonldjava.core.Context.parse(Context.java:169)
    at com.github.jsonldjava.core.Context.parse(Context.java:252)
    at com.github.jsonldjava.core.JsonLdApi.expand(JsonLdApi.java:534)
    at com.github.jsonldjava.core.JsonLdApi.expand(JsonLdApi.java:981)
    at com.github.jsonldjava.core.JsonLdProcessor.expand(JsonLdProcessor.java:146)
    at com.github.jsonldjava.core.JsonLdProcessor.toRDF(JsonLdProcessor.java:482)
    at org.apache.jena.riot.lang.JsonLDReader.read$(JsonLDReader.java:143)
    at org.apache.jena.riot.lang.JsonLDReader.read(JsonLDReader.java:83)
    at riotcmd.CmdLangParse.parseRIOT(CmdLangParse.java:286)
    at riotcmd.CmdLangParse.parseFile(CmdLangParse.java:202)
    at riotcmd.CmdLangParse.parseFile(CmdLangParse.java:184)
    at riotcmd.CmdLangParse.exec$(CmdLangParse.java:158)
    at riotcmd.CmdLangParse.exec(CmdLangParse.java:132)
    at jena.cmd.CmdMain.mainMethod(CmdMain.java:93)
    at jena.cmd.CmdMain.mainRun(CmdMain.java:58)
    at jena.cmd.CmdMain.mainRun(CmdMain.java:45)
    at riotcmd.riot.main(riot.java:34)

On 9 May 2016 at 12:16, François-Paul Servant
<fr...@gmail.com> wrote:
> Hi,
>
>> I get another JSON-LD error with using the @context
>> https://w3id.org/bundle/context that I need to check further what is
>> the cause of that (it works fine with JSON-LD Playground).
>>
>> org.apache.jena.riot.RiotException: loading remote context failed:
>> https://w3id.org/bundle/context
>>    at org.apache.jena.riot.system.ErrorHandlerFactory$ErrorHandlerStd.error(ErrorHandlerFactory.java:128)
>>    at org.apache.jena.riot.lang.JsonLDReader.read$(JsonLDReader.java:146)
>>    at org.apache.jena.riot.lang.JsonLDReader.read(JsonLDReader.java:83)
>>    at org.apache.jena.riot.RDFDataMgr.process(RDFDataMgr.java:861)
>>    at org.apache.jena.riot.RDFDataMgr.read(RDFDataMgr.java:259)
>>    at org.apache.jena.riot.RDFDataMgr.read(RDFDataMgr.java:245)
>>
>
> I don’t know whether it is the same thing, but I noticed (working with 3.1.1-SNAPSHOT) that following test, that attempts to read a simple jsonld document with an external context
>
> public class TestJsonLDReader {
>
>         @Test public final void test() {
>                 String jsonld = "{\"@id\":\"_:b0\",\"@type\":\"http://schema.org/Person\",\"name\":\"John Doe\",\"@context\":\"http://schema.org/\"}";
>                 StringReader reader = new StringReader(jsonld);
>                 Model m = ModelFactory.createDefaultModel();
>                 m.read(reader, null, "JSON-LD");
>                 m.write(System.out, "TURTLE");
>         }
>
> }
>
> gives:
>
> java.lang.NoSuchMethodError: org.apache.http.impl.client.cache.CacheConfig.custom()Lorg/apache/http/impl/client/cache/CacheConfig$Builder;
>         at com.github.jsonldjava.utils.JsonUtils.createDefaultHttpClient(JsonUtils.java:333)
>         at com.github.jsonldjava.utils.JsonUtils.getDefaultHttpClient(JsonUtils.java:323)
>         at com.github.jsonldjava.core.DocumentLoader.getHttpClient(DocumentLoader.java:84)
>         at com.github.jsonldjava.core.DocumentLoader.fromURL(DocumentLoader.java:59)
>         at com.github.jsonldjava.core.DocumentLoader.loadDocument(DocumentLoader.java:29)
>         at com.github.jsonldjava.core.Context.parse(Context.java:169)
>         at com.github.jsonldjava.core.Context.parse(Context.java:252)
>         at com.github.jsonldjava.core.JsonLdApi.expand(JsonLdApi.java:534)
>         at com.github.jsonldjava.core.JsonLdApi.expand(JsonLdApi.java:981)
>         at com.github.jsonldjava.core.JsonLdProcessor.expand(JsonLdProcessor.java:146)
>         at com.github.jsonldjava.core.JsonLdProcessor.toRDF(JsonLdProcessor.java:482)
>         at org.apache.jena.riot.lang.JsonLDReader.read$(JsonLDReader.java:143)
>         at org.apache.jena.riot.lang.JsonLDReader.read(JsonLDReader.java:64)
>
> It seems that there is a conflict between the version of http-client cache used by JSON-LD java 0.8.2 (4.5.1), and the one that wants jena (4.2.6). Jena seems to really want to choose its version, cf pom/xml:
>
> +       /*
> +      <dependency>
> +        <groupId>com.github.jsonld-java</groupId>
> +        <artifactId>jsonld-java</artifactId>
> +        <version>${ver.jsonldjava}</version>
> +        <exclusions>
> +          <exclusion>
> +            <groupId>commons-logging</groupId>
> +            <artifactId>commons-logging</artifactId>
> +          </exclusion>
> +          <!-- Exclude so we use our choice of versions -->
> +          <exclusion>
> +            <groupId>org.apache.httpcomponents</groupId>
> +            <artifactId>httpclient-cache</artifactId>
> +          </exclusion>
> +          <exclusion>
> +            <groupId>org.apache.httpcomponents</groupId>
> +            <artifactId>httpclient</artifactId>
> +          </exclusion>
>
> Best,
>
> fps
>



-- 
Stian Soiland-Reyes
Apache Taverna (incubating), Apache Commons RDF (incubating)
http://orcid.org/0000-0001-9842-9718

Re: [VOTE] Release Jena 3.1.0 (2nd proposed candidate)

Posted by Andy Seaborne <an...@apache.org>.

yes - the code need updating.

https://issues.apache.org/jira/browse/JENA-576

     Andy

On 09/05/16 12:16, Fran�ois-Paul Servant wrote:
> Hi,
>
>> I get another JSON-LD error with using the @context
>> https://w3id.org/bundle/context that I need to check further what is
>> the cause of that (it works fine with JSON-LD Playground).
>>
>> org.apache.jena.riot.RiotException: loading remote context failed:
>> https://w3id.org/bundle/context
>>     at org.apache.jena.riot.system.ErrorHandlerFactory$ErrorHandlerStd.error(ErrorHandlerFactory.java:128)
>>     at org.apache.jena.riot.lang.JsonLDReader.read$(JsonLDReader.java:146)
>>     at org.apache.jena.riot.lang.JsonLDReader.read(JsonLDReader.java:83)
>>     at org.apache.jena.riot.RDFDataMgr.process(RDFDataMgr.java:861)
>>     at org.apache.jena.riot.RDFDataMgr.read(RDFDataMgr.java:259)
>>     at org.apache.jena.riot.RDFDataMgr.read(RDFDataMgr.java:245)
>>
>
> I don\u2019t know whether it is the same thing, but I noticed (working with 3.1.1-SNAPSHOT) that following test, that attempts to read a simple jsonld document with an external context
>
> public class TestJsonLDReader {
>
> 	@Test public final void test() {
> 		String jsonld = "{\"@id\":\"_:b0\",\"@type\":\"http://schema.org/Person\",\"name\":\"John Doe\",\"@context\":\"http://schema.org/\"}";
> 		StringReader reader = new StringReader(jsonld);
> 		Model m = ModelFactory.createDefaultModel();
> 		m.read(reader, null, "JSON-LD");
> 		m.write(System.out, "TURTLE");
> 	}
>
> }
>
> gives:
>
> java.lang.NoSuchMethodError: org.apache.http.impl.client.cache.CacheConfig.custom()Lorg/apache/http/impl/client/cache/CacheConfig$Builder;
> 	at com.github.jsonldjava.utils.JsonUtils.createDefaultHttpClient(JsonUtils.java:333)
> 	at com.github.jsonldjava.utils.JsonUtils.getDefaultHttpClient(JsonUtils.java:323)
> 	at com.github.jsonldjava.core.DocumentLoader.getHttpClient(DocumentLoader.java:84)
> 	at com.github.jsonldjava.core.DocumentLoader.fromURL(DocumentLoader.java:59)
> 	at com.github.jsonldjava.core.DocumentLoader.loadDocument(DocumentLoader.java:29)
> 	at com.github.jsonldjava.core.Context.parse(Context.java:169)
> 	at com.github.jsonldjava.core.Context.parse(Context.java:252)
> 	at com.github.jsonldjava.core.JsonLdApi.expand(JsonLdApi.java:534)
> 	at com.github.jsonldjava.core.JsonLdApi.expand(JsonLdApi.java:981)
> 	at com.github.jsonldjava.core.JsonLdProcessor.expand(JsonLdProcessor.java:146)
> 	at com.github.jsonldjava.core.JsonLdProcessor.toRDF(JsonLdProcessor.java:482)
> 	at org.apache.jena.riot.lang.JsonLDReader.read$(JsonLDReader.java:143)
> 	at org.apache.jena.riot.lang.JsonLDReader.read(JsonLDReader.java:64)
>
> It seems that there is a conflict between the version of http-client cache used by JSON-LD java 0.8.2 (4.5.1), and the one that wants jena (4.2.6). Jena seems to really want to choose its version, cf pom/xml:
>
> +	/*
> +      <dependency>
> +        <groupId>com.github.jsonld-java</groupId>
> +        <artifactId>jsonld-java</artifactId>
> +        <version>${ver.jsonldjava}</version>
> +        <exclusions>
> +          <exclusion>
> +            <groupId>commons-logging</groupId>
> +            <artifactId>commons-logging</artifactId>
> +          </exclusion>
> +          <!-- Exclude so we use our choice of versions -->
> +          <exclusion>
> +            <groupId>org.apache.httpcomponents</groupId>
> +            <artifactId>httpclient-cache</artifactId>
> +          </exclusion>
> +          <exclusion>
> +            <groupId>org.apache.httpcomponents</groupId>
> +            <artifactId>httpclient</artifactId>
> +          </exclusion>
>
> Best,
>
> fps
>

Re: [VOTE] Release Jena 3.1.0 (2nd proposed candidate)

Posted by François-Paul Servant <fr...@gmail.com>.

Hi,

> I get another JSON-LD error with using the @context
> https://w3id.org/bundle/context that I need to check further what is
> the cause of that (it works fine with JSON-LD Playground).
> 
> org.apache.jena.riot.RiotException: loading remote context failed:
> https://w3id.org/bundle/context
>    at org.apache.jena.riot.system.ErrorHandlerFactory$ErrorHandlerStd.error(ErrorHandlerFactory.java:128)
>    at org.apache.jena.riot.lang.JsonLDReader.read$(JsonLDReader.java:146)
>    at org.apache.jena.riot.lang.JsonLDReader.read(JsonLDReader.java:83)
>    at org.apache.jena.riot.RDFDataMgr.process(RDFDataMgr.java:861)
>    at org.apache.jena.riot.RDFDataMgr.read(RDFDataMgr.java:259)
>    at org.apache.jena.riot.RDFDataMgr.read(RDFDataMgr.java:245)
> 

I don’t know whether it is the same thing, but I noticed (working with 3.1.1-SNAPSHOT) that following test, that attempts to read a simple jsonld document with an external context

public class TestJsonLDReader {

	@Test public final void test() {
		String jsonld = "{\"@id\":\"_:b0\",\"@type\":\"http://schema.org/Person\",\"name\":\"John Doe\",\"@context\":\"http://schema.org/\"}";
		StringReader reader = new StringReader(jsonld);
		Model m = ModelFactory.createDefaultModel();
		m.read(reader, null, "JSON-LD");
		m.write(System.out, "TURTLE");
	}

}

gives:

java.lang.NoSuchMethodError: org.apache.http.impl.client.cache.CacheConfig.custom()Lorg/apache/http/impl/client/cache/CacheConfig$Builder;
	at com.github.jsonldjava.utils.JsonUtils.createDefaultHttpClient(JsonUtils.java:333)
	at com.github.jsonldjava.utils.JsonUtils.getDefaultHttpClient(JsonUtils.java:323)
	at com.github.jsonldjava.core.DocumentLoader.getHttpClient(DocumentLoader.java:84)
	at com.github.jsonldjava.core.DocumentLoader.fromURL(DocumentLoader.java:59)
	at com.github.jsonldjava.core.DocumentLoader.loadDocument(DocumentLoader.java:29)
	at com.github.jsonldjava.core.Context.parse(Context.java:169)
	at com.github.jsonldjava.core.Context.parse(Context.java:252)
	at com.github.jsonldjava.core.JsonLdApi.expand(JsonLdApi.java:534)
	at com.github.jsonldjava.core.JsonLdApi.expand(JsonLdApi.java:981)
	at com.github.jsonldjava.core.JsonLdProcessor.expand(JsonLdProcessor.java:146)
	at com.github.jsonldjava.core.JsonLdProcessor.toRDF(JsonLdProcessor.java:482)
	at org.apache.jena.riot.lang.JsonLDReader.read$(JsonLDReader.java:143)
	at org.apache.jena.riot.lang.JsonLDReader.read(JsonLDReader.java:64)

It seems that there is a conflict between the version of http-client cache used by JSON-LD java 0.8.2 (4.5.1), and the one that wants jena (4.2.6). Jena seems to really want to choose its version, cf pom/xml:

+	/*
+      <dependency>
+        <groupId>com.github.jsonld-java</groupId>
+        <artifactId>jsonld-java</artifactId>
+        <version>${ver.jsonldjava}</version>
+        <exclusions>
+          <exclusion>
+            <groupId>commons-logging</groupId>
+            <artifactId>commons-logging</artifactId>
+          </exclusion>
+          <!-- Exclude so we use our choice of versions -->
+          <exclusion>
+            <groupId>org.apache.httpcomponents</groupId>
+            <artifactId>httpclient-cache</artifactId>
+          </exclusion>
+          <exclusion>
+            <groupId>org.apache.httpcomponents</groupId>
+            <artifactId>httpclient</artifactId>
+          </exclusion>

Best,

fps

Re: [VOTE] Release Jena 3.1.0 (2nd proposed candidate)

Posted by Stian Soiland-Reyes <st...@apache.org>.

-1 I'm afraid.

jena-osgi is missing (inclusion or dependency on) org/apache/xerces/util/XMLChar

which means I can no longer compile with jena-osgi as a Maven <dependency>.

Tested on http://github.com/apache/incubator-taverna-language/

Running org.apache.taverna.robundle.validator.ValidatorTest
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for
further details.
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.161
sec <<< FAILURE! - in
org.apache.taverna.robundle.validator.ValidatorTest
test(org.apache.taverna.robundle.validator.ValidatorTest)  Time
elapsed: 0.16 sec  <<< ERROR!
java.lang.NoClassDefFoundError: org/apache/xerces/util/XMLChar
    at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
    at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
    at org.apache.jena.rdf.model.impl.Util.notNameChar(Util.java:119)
    at org.apache.jena.rdf.model.impl.Util.splitNamespaceXML(Util.java:77)
    at org.apache.jena.graph.Node_URI.getLocalName(Node_URI.java:80)
    at org.apache.jena.rdf.model.impl.ResourceImpl.getLocalName(ResourceImpl.java:152)
    at org.apache.jena.rdf.model.impl.PropertyImpl.checkLocalName(PropertyImpl.java:64)
    at org.apache.jena.rdf.model.impl.PropertyImpl.<init>(PropertyImpl.java:72)
    at org.apache.jena.rdf.model.ResourceFactory$Impl.createProperty(ResourceFactory.java:335)
    at org.apache.jena.rdf.model.ResourceFactory.createProperty(ResourceFactory.java:180)
    at org.apache.jena.vocabulary.RDF.property(RDF.java:51)
    at org.apache.jena.vocabulary.RDF.<clinit>(RDF.java:64)
    at org.apache.jena.system.InitJenaCore.init(InitJenaCore.java:57)
    at org.apache.jena.system.InitJenaCore.start(InitJenaCore.java:31)
    at org.apache.jena.system.JenaSystem.lambda$init$1(JenaSystem.java:111)
    at java.util.ArrayList.forEach(ArrayList.java:1249)
    at org.apache.jena.system.JenaSystem.forEach(JenaSystem.java:186)
    at org.apache.jena.system.JenaSystem.forEach(JenaSystem.java:163)
    at org.apache.jena.system.JenaSystem.init(JenaSystem.java:109)
    at org.apache.jena.rdf.model.ModelFactory.<clinit>(ModelFactory.java:49)
    at org.apache.taverna.robundle.manifest.RDFToManifest.loadOntologyFromClasspath(RDFToManifest.java:315)
    at org.apache.taverna.robundle.manifest.RDFToManifest.loadDCT(RDFToManifest.java:262)
    at org.apache.taverna.robundle.manifest.RDFToManifest.loadOntologies(RDFToManifest.java:304)
    at org.apache.taverna.robundle.manifest.RDFToManifest.<init>(RDFToManifest.java:182)
    at org.apache.taverna.robundle.Bundle.readOrPopulateManifest(Bundle.java:114)
    at org.apache.taverna.robundle.Bundle.getManifest(Bundle.java:87)
    at org.apache.taverna.robundle.validator.RoValidator.validate(RoValidator.java:97)
    at org.apache.taverna.robundle.validator.RoValidator.<init>(RoValidator.java:80)
    at org.apache.taverna.robundle.validator.ValidatorTest.test(ValidatorTest.java:40)

subsequent calls then fail with

java.lang.NoClassDefFoundError: Could not initialize class
org.apache.jena.rdf.model.ModelFactory


I think this relates to Jaroslav' OSGi fixes - which I see now excludes xerces:
https://github.com/apache/jena/blob/master/apache-jena-osgi/jena-osgi/pom.xml#L242

this is fine - but if I'm to import Xerces I need to have a Maven
dependency on a Bundle that provides it or make sure it's part of the
boot delegation of my framework.

This change is not noted in the release note - I would be OK with the
change if the required workaround was described or the Maven POM for
jena-osgi had the appropriate <dependency>.



BTW - http://central.maven.org/maven2/xerces/xercesImpl/2.8.1/xercesImpl-2.8.1.jar
is not an OSGi bundle - and Jena depends on org.apache.xerces.impl.dv
which would not normally be exposed form a xerces bundle -

Adding

<dependency>
    <groupId>org.apache.servicemix.bundles</groupId>
    <artifactId>org.apache.servicemix.bundles.xerces</artifactId>
    <version>2.11.0_1</version>
</dependency>

seems to work, though. Perhaps this could be added to jena-osgi/pom.xml ?


I get another JSON-LD error with using the @context
https://w3id.org/bundle/context that I need to check further what is
the cause of that (it works fine with JSON-LD Playground).

org.apache.jena.riot.RiotException: loading remote context failed:
https://w3id.org/bundle/context
    at org.apache.jena.riot.system.ErrorHandlerFactory$ErrorHandlerStd.error(ErrorHandlerFactory.java:128)
    at org.apache.jena.riot.lang.JsonLDReader.read$(JsonLDReader.java:146)
    at org.apache.jena.riot.lang.JsonLDReader.read(JsonLDReader.java:83)
    at org.apache.jena.riot.RDFDataMgr.process(RDFDataMgr.java:861)
    at org.apache.jena.riot.RDFDataMgr.read(RDFDataMgr.java:259)
    at org.apache.jena.riot.RDFDataMgr.read(RDFDataMgr.java:245)

On 4 May 2016 at 20:53, Andy Seaborne <an...@apache.org> wrote:
> Hi,
>
> Here is a vote on a release of Jena 3.1.0
> (with Fuseki 2.4.0 and Fuseki 1.4.0).
>
> This is the second proposed candidate for this release.
>
> This fixes, from the previous proposed candidate
> 1/ Presence of binaries in the source-release
> 2/ Jump in large size of binary downloads due to javadoc inclusion
>
> * Dependency changes:
>
> Upgrades:
>   jsonld-java : 2.8.2
>   jackson 2.6.3
>   slf4j 1.7.20
>   dexx collections 0.6
>
> Key features listed below.
>
> Everyone, not just committers, is invited to test and vote.
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachejena-1012/
>
> Proposed dist/ area:
>     https://dist.apache.org/repos/dist/dev/jena/
>
> Keys:
>     https://svn.apache.org/repos/asf/jena/dist/KEYS
>
> Git commit (browser URL):
>     http://git-wip-us.apache.org/repos/asf/jena/commit/e7ee6bb6
>
> Git Commit Hash:
>     e7ee6bb69a5d7ce930a2529dd576a9ea209596a3
>
> Git Commit Tag:
>     jena-3.1.0-rc3
>
> Please vote to approve this release:
>
>     [ ] +1 Approve the release
>     [ ]  0 Don't care
>     [ ] -1 Don't release, because ...
>
> This vote will be open to at least
>
>      7th May 2016, 23:59 UTC
>
> If you expect to check the release but the 72 hour limit does not work for
> you, please email within the schedule above with an expected time and we can
> extend the vote period.
>
> Thanks,
>
>     Andy
>
> Checking needed:
>
> + does everything work on Linux?
> + does everything work on MS Windows?
> + does everything work on OS X?
> + are the GPG signatures fine?
> + are the checksums correct?
> + is there a source archive?
> + can the source archive really be built?
> + is there a correct LICENSE and NOTICE file in each artifact
>       (both source and binary artifacts)?
> + does the NOTICE file contain all necessary attributions?
> + have any licenses of dependencies changed due to upgrades?
>        if so have LICENSE and NOTICE been upgraded appropriately?
> + does the tag/commit in the SCM contain reproducible sources?
>
>
> ---------------------------
>
> Key features of the release:
>
> * In-memory txn dataset (Adam Soroka) (RC in 3.0.1)
>
> http://jena.staging.apache.org/documentation/rdf/datasets.html
>
> * Quads (Qihong Lin) (RC in 3.0.1)
>
> http://jena.staging.apache.org/documentation/query/construct-quad.html
>
> * DatasetGraphs & transactions integration
>
> * Alternative QueryParsers in jena-text
>
> * new module jena-cmds
> "jena.*"
>
> * Fuseki: Multiple service per file, shared datasets
>
> * Logging
> log4j marked <optional>
>
> * New custom functions and aggregate functions
> Added:
> * afn:springf (contribution from Alessandro Seganti)
> * The XQuery/XPath Functions and Operators "math:" functions
> * Custom aggregates for stdev etc. (also STDEV etc as keywords).
>
> * FactoryRDF
> Parsing RDF now saves space by interning RDFTerms created
> during a each parser run.
>
> * OSGi fixes (Jaroslav Pullmann)
>
> * General maintenance: about 80 JIRA.
>



-- 
Stian Soiland-Reyes
Apache Taverna (incubating), Apache Commons RDF (incubating)
http://orcid.org/0000-0001-9842-9718

Re: [VOTE] Release Jena 3.1.0 (2nd proposed candidate)

Posted by "Bruno P. Kinoshita" <ki...@apache.org>.

Thanks Andy!

I'm watching that issue. Will have spare time this week/weekend. In case no one is working on this, I'll see if I can have some fun with time zones.

Here's my +1

Bruno


----- Original Message -----
> From: Andy Seaborne <an...@apache.org>
> To: dev@jena.apache.org
> Sent: Monday, 9 May 2016 10:17 PM
> Subject: Re: [VOTE] Release Jena 3.1.0 (2nd proposed candidate)
> 
> On 09/05/16 11:08, Bruno P. Kinoshita wrote:
>> 
>> 
>>  Hi Andy,
>> 
>>  Noticed my e-mails are missing the formatting, so trying to post this one 
> as plain-text.
>> 
>>  Thanks for the tips regarding the Eclipse set up. Will give it another try.
>>>  Would you be happy to vote +1 if we raise a JIRA to fix this test 
> issue?
>> 
>>  Sure thing. Should I fill the issue
> 
> Done!
> https://issues.apache.org/jira/browse/JENA-1175
> 
>>  and re-cast the vote?
> 
> Please do.
> 
> As RM, I'm happy that it's the test that's at fault, not the 
> functionality.
> 
> It's good the tests show it in the first place!
> 
> 
>      Andy
> 
>> 
>>  Bruno
>> 
>>>  ________________________________
>>>  From: Andy Seaborne <an...@apache.org>
>>>  To: dev@jena.apache.org
>>>  Sent: Monday, 9 May 2016 10:04 PM
>>>  Subject: Re: [VOTE] Release Jena 3.1.0 (2nd proposed candidate)
>>> 
>>> 
>>>  Hi Bruno,
>>> 
>>>  On 09/05/16 10:39, Bruno P. Kinoshita wrote:
>>>>  Hi,
>>>>  I have one test failing at the moment:
>>> 
>>>  TestFunctions.exprSprintf_05
>>> 
>>>>  Running org.apache.jena.sparql.expr.TS_ExprTests run: 1255, 
> Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.277 sec <<< 
> FAILURE! - in 
> org.apache.jena.sparql.expr.TS_ExprexprSprintf_05(org.apache.jena.sparql.expr.TestFunctions)  
> Time elapsed: 0.006 sec  <<< FAILURE!java.lang.AssertionError: 
> expected:<"10 14,2005"> but was:<"10 15,2005"> 
> at org.junit.Assert.fail(Assert.java:88) at 
> org.junit.Assert.failNotEquals(Assert.java:834) at 
> org.junit.Assert.assertEquals(Assert.java:118) at 
> org.junit.Assert.assertEquals(Assert.java:144) at 
> org.apache.jena.sparql.expr.TestFunctions.test(TestFunctions.java:270) at 
> org.apache.jena.sparql.expr.TestFunctions.exprSprintf_05(TestFunctions.java:82)
>>>>  Trying to import the project in Eclipse to try to see what's 
> going on, but already spent some time battling Eclipse + maven. Looks like I 
> have some problems with shaded guava dependencies. I remember I had to close the 
> shaded-guava project in my workspace? But now it won't build with the 
> project closed either.
>>> 
>>>  The way I work is to not import at all the shaded guava and only
>>>  import/have open the projects from jena-base.
>>> 
>>>  (Actually, I only have some modules open as needed to make navigation
>>>  easier)
>>> 
>>>>  Anyone building in Eclipse that could shed some light?
>>>>  I believe this test is failing due to my timezone?
>>> 
>>>  Yes - now I look at the test, that seems to be the case:
>>> 
>>>  The test is comparing:
>>> 
>>>  NodeValue.makeDateTime("2005-10-14T13:09:43Z")
>>> 
>>>  via
>>> 
>>>  afn:sprintf('%1$tm %1$te,%1$tY', ...)
>>> 
>>>  with
>>> 
>>>  "10 14,2005"
>>> 
>>>  and yes, that's not going to work for your timezone where
>>>  "2005-10-14T13:09:43Z" is "10 15,2005" local.
>>> 
>>>  It is supposed to be locale sensitive so it's the test that's 
> wrong.
>>> 
>>>  Would you be happy to vote +1 if we raise a JIRA to fix this test 
> issue?
>>> 
>>>       Andy
>>> 
>>> 
>>>>  I'm on:
>>>>  kinow:~/Development/java/jena/jena$ timedatectl      Local time: 
> Mon 2016-05-09 21:38:18 NZST  Universal time: Mon 2016-05-09 09:38:18 UTC        
> RTC time: Mon 2016-05-09 09:38:18       Time zone: Pacific/Auckland (NZST, 
> +1200) Network time on: yesNTP synchronized: yes RTC in local TZ: no
>>>>  And Java environment:
>>>>  kinow:~/Development/java/jena/jena$ mvn -vApache Maven 3.3.9 
> (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-11T05:41:47+13:00)Maven home: 
> /opt/mavenJava version: 1.8.0_91, vendor: Oracle CorporationJava home: 
> /usr/lib/jvm/java-8-oracle/jreDefault locale: en_NZ, platform encoding: UTF-8OS 
> name: "linux", version: "4.4.0-22-generic", arch: 
> "amd64", family: "unix"
>>>>  (Ubuntu 16.04 + Java 8 + Maven 3)
>>>>  CheersBruno
>>> 
>>> 
>>> 
>>>> 
>>>>          From: Andy Seaborne <an...@apache.org>
>>>>     To: dev@jena.apache.org
>>>>     Sent: Thursday, 5 May 2016 7:53 AM
>>>>     Subject: [VOTE] Release Jena 3.1.0 (2nd proposed candidate)
>>>> 
>>>>  Hi,
>>>> 
>>>>  Here is a vote on a release of Jena 3.1.0
>>>>  (with Fuseki 2.4.0 and Fuseki 1.4.0).
>>>> 
>>>>  This is the second proposed candidate for this release.
>>>> 
>>>>  This fixes, from the previous proposed candidate
>>>>  1/ Presence of binaries in the source-release
>>>>  2/ Jump in large size of binary downloads due to javadoc inclusion
>>>> 
>>>>  * Dependency changes:
>>>> 
>>>>  Upgrades:
>>>>      jsonld-java : 2.8.2
>>>>      jackson 2.6.3
>>>>      slf4j 1.7.20
>>>>      dexx collections 0.6
>>>> 
>>>>  Key features listed below.
>>>> 
>>>>  Everyone, not just committers, is invited to test and vote.
>>>> 
>>>>  Staging repository:
>>>> 
> https://repository.apache.org/content/repositories/orgapachejena-1012/
>>>> 
>>>>  Proposed dist/ area:
>>>>       https://dist.apache.org/repos/dist/dev/jena/
>>>> 
>>>>  Keys:
>>>>       https://svn.apache.org/repos/asf/jena/dist/KEYS
>>>> 
>>>>  Git commit (browser URL):
>>>>       http://git-wip-us.apache.org/repos/asf/jena/commit/e7ee6bb6
>>>> 
>>>>  Git Commit Hash:
>>>>        e7ee6bb69a5d7ce930a2529dd576a9ea209596a3
>>>> 
>>>>  Git Commit Tag:
>>>>        jena-3.1.0-rc3
>>>> 
>>>>  Please vote to approve this release:
>>>> 
>>>>        [ ] +1 Approve the release
>>>>        [ ]  0 Don't care
>>>>        [ ] -1 Don't release, because ...
>>>> 
>>>>  This vote will be open to at least
>>>> 
>>>>          7th May 2016, 23:59 UTC
>>>> 
>>>>  If you expect to check the release but the 72 hour limit does not 
> work
>>>>  for you, please email within the schedule above with an expected 
> time
>>>>  and we can extend the vote period.
>>>> 
>>>>  Thanks,
>>>> 
>>>>        Andy
>>>> 
>>>>  Checking needed:
>>>> 
>>>>  + does everything work on Linux?
>>>>  + does everything work on MS Windows?
>>>>  + does everything work on OS X?
>>>>  + are the GPG signatures fine?
>>>>  + are the checksums correct?
>>>>  + is there a source archive?
>>>>  + can the source archive really be built?
>>>>  + is there a correct LICENSE and NOTICE file in each artifact
>>>>          (both source and binary artifacts)?
>>>>  + does the NOTICE file contain all necessary attributions?
>>>>  + have any licenses of dependencies changed due to upgrades?
>>>>            if so have LICENSE and NOTICE been upgraded 
> appropriately?
>>>>  + does the tag/commit in the SCM contain reproducible sources?
>>>> 
>>>> 
>>>>  ---------------------------
>>>> 
>>>>  Key features of the release:
>>>> 
>>>>  * In-memory txn dataset (Adam Soroka) (RC in 3.0.1)
>>>> 
>>>>  http://jena.staging.apache.org/documentation/rdf/datasets.html
>>>> 
>>>>  * Quads (Qihong Lin) (RC in 3.0.1)
>>>> 
>>>> 
> http://jena.staging.apache.org/documentation/query/construct-quad.html
>>>> 
>>>>  * DatasetGraphs & transactions integration
>>>> 
>>>>  * Alternative QueryParsers in jena-text
>>>> 
>>>>  * new module jena-cmds
>>>>  "jena.*"
>>>> 
>>>>  * Fuseki: Multiple service per file, shared datasets
>>>> 
>>>>  * Logging
>>>>  log4j marked <optional>
>>>> 
>>>>  * New custom functions and aggregate functions
>>>>  Added:
>>>>  * afn:springf (contribution from Alessandro Seganti)
>>>>  * The XQuery/XPath Functions and Operators "math:" 
> functions
>>>>  * Custom aggregates for stdev etc. (also STDEV etc as keywords).
>>>> 
>>>>  * FactoryRDF
>>>>  Parsing RDF now saves space by interning RDFTerms created
>>>>  during a each parser run.
>>>> 
>>>>  * OSGi fixes (Jaroslav Pullmann)
>>>> 
>>>>  * General maintenance: about 80 JIRA.
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>> 
>>> 
>>> 
>>> 
>

Re: [VOTE] Release Jena 3.1.0 (2nd proposed candidate)

Posted by Andy Seaborne <an...@apache.org>.

On 09/05/16 11:08, Bruno P. Kinoshita wrote:
>
>
> Hi Andy,
>
> Noticed my e-mails are missing the formatting, so trying to post this one as plain-text.
>
> Thanks for the tips regarding the Eclipse set up. Will give it another try.
>> Would you be happy to vote +1 if we raise a JIRA to fix this test issue?
>
> Sure thing. Should I fill the issue

Done!
https://issues.apache.org/jira/browse/JENA-1175

> and re-cast the vote?

Please do.

As RM, I'm happy that it's the test that's at fault, not the functionality.

It's good the tests show it in the first place!

     Andy

>
> Bruno
>
>> ________________________________
>> From: Andy Seaborne <an...@apache.org>
>> To: dev@jena.apache.org
>> Sent: Monday, 9 May 2016 10:04 PM
>> Subject: Re: [VOTE] Release Jena 3.1.0 (2nd proposed candidate)
>>
>>
>> Hi Bruno,
>>
>> On 09/05/16 10:39, Bruno P. Kinoshita wrote:
>>> Hi,
>>> I have one test failing at the moment:
>>
>> TestFunctions.exprSprintf_05
>>
>>> Running org.apache.jena.sparql.expr.TS_ExprTests run: 1255, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.277 sec <<< FAILURE! - in org.apache.jena.sparql.expr.TS_ExprexprSprintf_05(org.apache.jena.sparql.expr.TestFunctions)  Time elapsed: 0.006 sec  <<< FAILURE!java.lang.AssertionError: expected:<"10 14,2005"> but was:<"10 15,2005"> at org.junit.Assert.fail(Assert.java:88) at org.junit.Assert.failNotEquals(Assert.java:834) at org.junit.Assert.assertEquals(Assert.java:118) at org.junit.Assert.assertEquals(Assert.java:144) at org.apache.jena.sparql.expr.TestFunctions.test(TestFunctions.java:270) at org.apache.jena.sparql.expr.TestFunctions.exprSprintf_05(TestFunctions.java:82)
>>> Trying to import the project in Eclipse to try to see what's going on, but already spent some time battling Eclipse + maven. Looks like I have some problems with shaded guava dependencies. I remember I had to close the shaded-guava project in my workspace? But now it won't build with the project closed either.
>>
>> The way I work is to not import at all the shaded guava and only
>> import/have open the projects from jena-base.
>>
>> (Actually, I only have some modules open as needed to make navigation
>> easier)
>>
>>> Anyone building in Eclipse that could shed some light?
>>> I believe this test is failing due to my timezone?
>>
>> Yes - now I look at the test, that seems to be the case:
>>
>> The test is comparing:
>>
>> NodeValue.makeDateTime("2005-10-14T13:09:43Z")
>>
>> via
>>
>> afn:sprintf('%1$tm %1$te,%1$tY', ...)
>>
>> with
>>
>> "10 14,2005"
>>
>> and yes, that's not going to work for your timezone where
>> "2005-10-14T13:09:43Z" is "10 15,2005" local.
>>
>> It is supposed to be locale sensitive so it's the test that's wrong.
>>
>> Would you be happy to vote +1 if we raise a JIRA to fix this test issue?
>>
>>      Andy
>>
>>
>>> I'm on:
>>> kinow:~/Development/java/jena/jena$ timedatectl      Local time: Mon 2016-05-09 21:38:18 NZST  Universal time: Mon 2016-05-09 09:38:18 UTC        RTC time: Mon 2016-05-09 09:38:18       Time zone: Pacific/Auckland (NZST, +1200) Network time on: yesNTP synchronized: yes RTC in local TZ: no
>>> And Java environment:
>>> kinow:~/Development/java/jena/jena$ mvn -vApache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-11T05:41:47+13:00)Maven home: /opt/mavenJava version: 1.8.0_91, vendor: Oracle CorporationJava home: /usr/lib/jvm/java-8-oracle/jreDefault locale: en_NZ, platform encoding: UTF-8OS name: "linux", version: "4.4.0-22-generic", arch: "amd64", family: "unix"
>>> (Ubuntu 16.04 + Java 8 + Maven 3)
>>> CheersBruno
>>
>>
>>
>>>
>>>         From: Andy Seaborne <an...@apache.org>
>>>    To: dev@jena.apache.org
>>>    Sent: Thursday, 5 May 2016 7:53 AM
>>>    Subject: [VOTE] Release Jena 3.1.0 (2nd proposed candidate)
>>>
>>> Hi,
>>>
>>> Here is a vote on a release of Jena 3.1.0
>>> (with Fuseki 2.4.0 and Fuseki 1.4.0).
>>>
>>> This is the second proposed candidate for this release.
>>>
>>> This fixes, from the previous proposed candidate
>>> 1/ Presence of binaries in the source-release
>>> 2/ Jump in large size of binary downloads due to javadoc inclusion
>>>
>>> * Dependency changes:
>>>
>>> Upgrades:
>>>     jsonld-java : 2.8.2
>>>     jackson 2.6.3
>>>     slf4j 1.7.20
>>>     dexx collections 0.6
>>>
>>> Key features listed below.
>>>
>>> Everyone, not just committers, is invited to test and vote.
>>>
>>> Staging repository:
>>> https://repository.apache.org/content/repositories/orgapachejena-1012/
>>>
>>> Proposed dist/ area:
>>>       https://dist.apache.org/repos/dist/dev/jena/
>>>
>>> Keys:
>>>       https://svn.apache.org/repos/asf/jena/dist/KEYS
>>>
>>> Git commit (browser URL):
>>>       http://git-wip-us.apache.org/repos/asf/jena/commit/e7ee6bb6
>>>
>>> Git Commit Hash:
>>>       e7ee6bb69a5d7ce930a2529dd576a9ea209596a3
>>>
>>> Git Commit Tag:
>>>       jena-3.1.0-rc3
>>>
>>> Please vote to approve this release:
>>>
>>>       [ ] +1 Approve the release
>>>       [ ]  0 Don't care
>>>       [ ] -1 Don't release, because ...
>>>
>>> This vote will be open to at least
>>>
>>>         7th May 2016, 23:59 UTC
>>>
>>> If you expect to check the release but the 72 hour limit does not work
>>> for you, please email within the schedule above with an expected time
>>> and we can extend the vote period.
>>>
>>> Thanks,
>>>
>>>       Andy
>>>
>>> Checking needed:
>>>
>>> + does everything work on Linux?
>>> + does everything work on MS Windows?
>>> + does everything work on OS X?
>>> + are the GPG signatures fine?
>>> + are the checksums correct?
>>> + is there a source archive?
>>> + can the source archive really be built?
>>> + is there a correct LICENSE and NOTICE file in each artifact
>>>         (both source and binary artifacts)?
>>> + does the NOTICE file contain all necessary attributions?
>>> + have any licenses of dependencies changed due to upgrades?
>>>           if so have LICENSE and NOTICE been upgraded appropriately?
>>> + does the tag/commit in the SCM contain reproducible sources?
>>>
>>>
>>> ---------------------------
>>>
>>> Key features of the release:
>>>
>>> * In-memory txn dataset (Adam Soroka) (RC in 3.0.1)
>>>
>>> http://jena.staging.apache.org/documentation/rdf/datasets.html
>>>
>>> * Quads (Qihong Lin) (RC in 3.0.1)
>>>
>>> http://jena.staging.apache.org/documentation/query/construct-quad.html
>>>
>>> * DatasetGraphs & transactions integration
>>>
>>> * Alternative QueryParsers in jena-text
>>>
>>> * new module jena-cmds
>>> "jena.*"
>>>
>>> * Fuseki: Multiple service per file, shared datasets
>>>
>>> * Logging
>>> log4j marked <optional>
>>>
>>> * New custom functions and aggregate functions
>>> Added:
>>> * afn:springf (contribution from Alessandro Seganti)
>>> * The XQuery/XPath Functions and Operators "math:" functions
>>> * Custom aggregates for stdev etc. (also STDEV etc as keywords).
>>>
>>> * FactoryRDF
>>> Parsing RDF now saves space by interning RDFTerms created
>>> during a each parser run.
>>>
>>> * OSGi fixes (Jaroslav Pullmann)
>>>
>>> * General maintenance: about 80 JIRA.
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>

Re: [VOTE] Release Jena 3.1.0 (2nd proposed candidate)

Posted by "Bruno P. Kinoshita" <ki...@apache.org>.


Hi Andy,

Noticed my e-mails are missing the formatting, so trying to post this one as plain-text.

Thanks for the tips regarding the Eclipse set up. Will give it another try. 
>Would you be happy to vote +1 if we raise a JIRA to fix this test issue?

Sure thing. Should I fill the issue and re-cast the vote?

Bruno

>________________________________
> From: Andy Seaborne <an...@apache.org>
>To: dev@jena.apache.org 
>Sent: Monday, 9 May 2016 10:04 PM
>Subject: Re: [VOTE] Release Jena 3.1.0 (2nd proposed candidate)
> 
>
>Hi Bruno,
>
>On 09/05/16 10:39, Bruno P. Kinoshita wrote:
>> Hi,
>> I have one test failing at the moment:
>
>TestFunctions.exprSprintf_05
>
>> Running org.apache.jena.sparql.expr.TS_ExprTests run: 1255, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.277 sec <<< FAILURE! - in org.apache.jena.sparql.expr.TS_ExprexprSprintf_05(org.apache.jena.sparql.expr.TestFunctions)  Time elapsed: 0.006 sec  <<< FAILURE!java.lang.AssertionError: expected:<"10 14,2005"> but was:<"10 15,2005"> at org.junit.Assert.fail(Assert.java:88) at org.junit.Assert.failNotEquals(Assert.java:834) at org.junit.Assert.assertEquals(Assert.java:118) at org.junit.Assert.assertEquals(Assert.java:144) at org.apache.jena.sparql.expr.TestFunctions.test(TestFunctions.java:270) at org.apache.jena.sparql.expr.TestFunctions.exprSprintf_05(TestFunctions.java:82)
>> Trying to import the project in Eclipse to try to see what's going on, but already spent some time battling Eclipse + maven. Looks like I have some problems with shaded guava dependencies. I remember I had to close the shaded-guava project in my workspace? But now it won't build with the project closed either.
>
>The way I work is to not import at all the shaded guava and only 
>import/have open the projects from jena-base.
>
>(Actually, I only have some modules open as needed to make navigation 
>easier)
>
>> Anyone building in Eclipse that could shed some light?
>> I believe this test is failing due to my timezone?
>
>Yes - now I look at the test, that seems to be the case:
>
>The test is comparing:
>
>NodeValue.makeDateTime("2005-10-14T13:09:43Z")
>
>via
>
>afn:sprintf('%1$tm %1$te,%1$tY', ...)
>
>with
>
>"10 14,2005"
>
>and yes, that's not going to work for your timezone where 
>"2005-10-14T13:09:43Z" is "10 15,2005" local.
>
>It is supposed to be locale sensitive so it's the test that's wrong.
>
>Would you be happy to vote +1 if we raise a JIRA to fix this test issue?
>
>     Andy
>
>
>> I'm on:
>> kinow:~/Development/java/jena/jena$ timedatectl      Local time: Mon 2016-05-09 21:38:18 NZST  Universal time: Mon 2016-05-09 09:38:18 UTC        RTC time: Mon 2016-05-09 09:38:18       Time zone: Pacific/Auckland (NZST, +1200) Network time on: yesNTP synchronized: yes RTC in local TZ: no
>> And Java environment:
>> kinow:~/Development/java/jena/jena$ mvn -vApache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-11T05:41:47+13:00)Maven home: /opt/mavenJava version: 1.8.0_91, vendor: Oracle CorporationJava home: /usr/lib/jvm/java-8-oracle/jreDefault locale: en_NZ, platform encoding: UTF-8OS name: "linux", version: "4.4.0-22-generic", arch: "amd64", family: "unix"
>> (Ubuntu 16.04 + Java 8 + Maven 3)
>> CheersBruno
>
>
>
>>
>>        From: Andy Seaborne <an...@apache.org>
>>   To: dev@jena.apache.org
>>   Sent: Thursday, 5 May 2016 7:53 AM
>>   Subject: [VOTE] Release Jena 3.1.0 (2nd proposed candidate)
>>
>> Hi,
>>
>> Here is a vote on a release of Jena 3.1.0
>> (with Fuseki 2.4.0 and Fuseki 1.4.0).
>>
>> This is the second proposed candidate for this release.
>>
>> This fixes, from the previous proposed candidate
>> 1/ Presence of binaries in the source-release
>> 2/ Jump in large size of binary downloads due to javadoc inclusion
>>
>> * Dependency changes:
>>
>> Upgrades:
>>    jsonld-java : 2.8.2
>>    jackson 2.6.3
>>    slf4j 1.7.20
>>    dexx collections 0.6
>>
>> Key features listed below.
>>
>> Everyone, not just committers, is invited to test and vote.
>>
>> Staging repository:
>> https://repository.apache.org/content/repositories/orgapachejena-1012/
>>
>> Proposed dist/ area:
>>      https://dist.apache.org/repos/dist/dev/jena/
>>
>> Keys:
>>      https://svn.apache.org/repos/asf/jena/dist/KEYS
>>
>> Git commit (browser URL):
>>      http://git-wip-us.apache.org/repos/asf/jena/commit/e7ee6bb6
>>
>> Git Commit Hash:
>>      e7ee6bb69a5d7ce930a2529dd576a9ea209596a3
>>
>> Git Commit Tag:
>>      jena-3.1.0-rc3
>>
>> Please vote to approve this release:
>>
>>      [ ] +1 Approve the release
>>      [ ]  0 Don't care
>>      [ ] -1 Don't release, because ...
>>
>> This vote will be open to at least
>>
>>        7th May 2016, 23:59 UTC
>>
>> If you expect to check the release but the 72 hour limit does not work
>> for you, please email within the schedule above with an expected time
>> and we can extend the vote period.
>>
>> Thanks,
>>
>>      Andy
>>
>> Checking needed:
>>
>> + does everything work on Linux?
>> + does everything work on MS Windows?
>> + does everything work on OS X?
>> + are the GPG signatures fine?
>> + are the checksums correct?
>> + is there a source archive?
>> + can the source archive really be built?
>> + is there a correct LICENSE and NOTICE file in each artifact
>>        (both source and binary artifacts)?
>> + does the NOTICE file contain all necessary attributions?
>> + have any licenses of dependencies changed due to upgrades?
>>          if so have LICENSE and NOTICE been upgraded appropriately?
>> + does the tag/commit in the SCM contain reproducible sources?
>>
>>
>> ---------------------------
>>
>> Key features of the release:
>>
>> * In-memory txn dataset (Adam Soroka) (RC in 3.0.1)
>>
>> http://jena.staging.apache.org/documentation/rdf/datasets.html
>>
>> * Quads (Qihong Lin) (RC in 3.0.1)
>>
>> http://jena.staging.apache.org/documentation/query/construct-quad.html
>>
>> * DatasetGraphs & transactions integration
>>
>> * Alternative QueryParsers in jena-text
>>
>> * new module jena-cmds
>> "jena.*"
>>
>> * Fuseki: Multiple service per file, shared datasets
>>
>> * Logging
>> log4j marked <optional>
>>
>> * New custom functions and aggregate functions
>> Added:
>> * afn:springf (contribution from Alessandro Seganti)
>> * The XQuery/XPath Functions and Operators "math:" functions
>> * Custom aggregates for stdev etc. (also STDEV etc as keywords).
>>
>> * FactoryRDF
>> Parsing RDF now saves space by interning RDFTerms created
>> during a each parser run.
>>
>> * OSGi fixes (Jaroslav Pullmann)
>>
>> * General maintenance: about 80 JIRA.
>>
>>
>>
>>
>>
>
>
>
>

Re: [VOTE] Release Jena 3.1.0 (2nd proposed candidate)

Posted by Andy Seaborne <an...@apache.org>.

Hi Bruno,

On 09/05/16 10:39, Bruno P. Kinoshita wrote:
> Hi,
> I have one test failing at the moment:

TestFunctions.exprSprintf_05

> Running org.apache.jena.sparql.expr.TS_ExprTests run: 1255, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.277 sec <<< FAILURE! - in org.apache.jena.sparql.expr.TS_ExprexprSprintf_05(org.apache.jena.sparql.expr.TestFunctions)  Time elapsed: 0.006 sec  <<< FAILURE!java.lang.AssertionError: expected:<"10 14,2005"> but was:<"10 15,2005"> at org.junit.Assert.fail(Assert.java:88) at org.junit.Assert.failNotEquals(Assert.java:834) at org.junit.Assert.assertEquals(Assert.java:118) at org.junit.Assert.assertEquals(Assert.java:144) at org.apache.jena.sparql.expr.TestFunctions.test(TestFunctions.java:270) at org.apache.jena.sparql.expr.TestFunctions.exprSprintf_05(TestFunctions.java:82)
> Trying to import the project in Eclipse to try to see what's going on, but already spent some time battling Eclipse + maven. Looks like I have some problems with shaded guava dependencies. I remember I had to close the shaded-guava project in my workspace? But now it won't build with the project closed either.

The way I work is to not import at all the shaded guava and only 
import/have open the projects from jena-base.

(Actually, I only have some modules open as needed to make navigation 
easier)

> Anyone building in Eclipse that could shed some light?
> I believe this test is failing due to my timezone?

Yes - now I look at the test, that seems to be the case:

The test is comparing:

NodeValue.makeDateTime("2005-10-14T13:09:43Z")

via

afn:sprintf('%1$tm %1$te,%1$tY', ...)

with

"10 14,2005"

and yes, that's not going to work for your timezone where 
"2005-10-14T13:09:43Z" is "10 15,2005" local.

It is supposed to be locale sensitive so it's the test that's wrong.

Would you be happy to vote +1 if we raise a JIRA to fix this test issue?

     Andy

> I'm on:
> kinow:~/Development/java/jena/jena$ timedatectl      Local time: Mon 2016-05-09 21:38:18 NZST  Universal time: Mon 2016-05-09 09:38:18 UTC        RTC time: Mon 2016-05-09 09:38:18       Time zone: Pacific/Auckland (NZST, +1200) Network time on: yesNTP synchronized: yes RTC in local TZ: no
> And Java environment:
> kinow:~/Development/java/jena/jena$ mvn -vApache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-11T05:41:47+13:00)Maven home: /opt/mavenJava version: 1.8.0_91, vendor: Oracle CorporationJava home: /usr/lib/jvm/java-8-oracle/jreDefault locale: en_NZ, platform encoding: UTF-8OS name: "linux", version: "4.4.0-22-generic", arch: "amd64", family: "unix"
> (Ubuntu 16.04 + Java 8 + Maven 3)
> CheersBruno



>
>        From: Andy Seaborne <an...@apache.org>
>   To: dev@jena.apache.org
>   Sent: Thursday, 5 May 2016 7:53 AM
>   Subject: [VOTE] Release Jena 3.1.0 (2nd proposed candidate)
>
> Hi,
>
> Here is a vote on a release of Jena 3.1.0
> (with Fuseki 2.4.0 and Fuseki 1.4.0).
>
> This is the second proposed candidate for this release.
>
> This fixes, from the previous proposed candidate
> 1/ Presence of binaries in the source-release
> 2/ Jump in large size of binary downloads due to javadoc inclusion
>
> * Dependency changes:
>
> Upgrades:
>    jsonld-java : 2.8.2
>    jackson 2.6.3
>    slf4j 1.7.20
>    dexx collections 0.6
>
> Key features listed below.
>
> Everyone, not just committers, is invited to test and vote.
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachejena-1012/
>
> Proposed dist/ area:
>      https://dist.apache.org/repos/dist/dev/jena/
>
> Keys:
>      https://svn.apache.org/repos/asf/jena/dist/KEYS
>
> Git commit (browser URL):
>      http://git-wip-us.apache.org/repos/asf/jena/commit/e7ee6bb6
>
> Git Commit Hash:
>      e7ee6bb69a5d7ce930a2529dd576a9ea209596a3
>
> Git Commit Tag:
>      jena-3.1.0-rc3
>
> Please vote to approve this release:
>
>      [ ] +1 Approve the release
>      [ ]  0 Don't care
>      [ ] -1 Don't release, because ...
>
> This vote will be open to at least
>
>        7th May 2016, 23:59 UTC
>
> If you expect to check the release but the 72 hour limit does not work
> for you, please email within the schedule above with an expected time
> and we can extend the vote period.
>
> Thanks,
>
>      Andy
>
> Checking needed:
>
> + does everything work on Linux?
> + does everything work on MS Windows?
> + does everything work on OS X?
> + are the GPG signatures fine?
> + are the checksums correct?
> + is there a source archive?
> + can the source archive really be built?
> + is there a correct LICENSE and NOTICE file in each artifact
>        (both source and binary artifacts)?
> + does the NOTICE file contain all necessary attributions?
> + have any licenses of dependencies changed due to upgrades?
>          if so have LICENSE and NOTICE been upgraded appropriately?
> + does the tag/commit in the SCM contain reproducible sources?
>
>
> ---------------------------
>
> Key features of the release:
>
> * In-memory txn dataset (Adam Soroka) (RC in 3.0.1)
>
> http://jena.staging.apache.org/documentation/rdf/datasets.html
>
> * Quads (Qihong Lin) (RC in 3.0.1)
>
> http://jena.staging.apache.org/documentation/query/construct-quad.html
>
> * DatasetGraphs & transactions integration
>
> * Alternative QueryParsers in jena-text
>
> * new module jena-cmds
> "jena.*"
>
> * Fuseki: Multiple service per file, shared datasets
>
> * Logging
> log4j marked <optional>
>
> * New custom functions and aggregate functions
> Added:
> * afn:springf (contribution from Alessandro Seganti)
> * The XQuery/XPath Functions and Operators "math:" functions
> * Custom aggregates for stdev etc. (also STDEV etc as keywords).
>
> * FactoryRDF
> Parsing RDF now saves space by interning RDFTerms created
> during a each parser run.
>
> * OSGi fixes (Jaroslav Pullmann)
>
> * General maintenance: about 80 JIRA.
>
>
>
>
>

Re: [VOTE] Release Jena 3.1.0 (2nd proposed candidate)

Posted by "Bruno P. Kinoshita" <ki...@apache.org>.

Hi,
I have one test failing at the moment:
Running org.apache.jena.sparql.expr.TS_ExprTests run: 1255, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.277 sec <<< FAILURE! - in org.apache.jena.sparql.expr.TS_ExprexprSprintf_05(org.apache.jena.sparql.expr.TestFunctions)  Time elapsed: 0.006 sec  <<< FAILURE!java.lang.AssertionError: expected:<"10 14,2005"> but was:<"10 15,2005"> at org.junit.Assert.fail(Assert.java:88) at org.junit.Assert.failNotEquals(Assert.java:834) at org.junit.Assert.assertEquals(Assert.java:118) at org.junit.Assert.assertEquals(Assert.java:144) at org.apache.jena.sparql.expr.TestFunctions.test(TestFunctions.java:270) at org.apache.jena.sparql.expr.TestFunctions.exprSprintf_05(TestFunctions.java:82)
Trying to import the project in Eclipse to try to see what's going on, but already spent some time battling Eclipse + maven. Looks like I have some problems with shaded guava dependencies. I remember I had to close the shaded-guava project in my workspace? But now it won't build with the project closed either.
Anyone building in Eclipse that could shed some light?
I believe this test is failing due to my timezone? I'm on:
kinow:~/Development/java/jena/jena$ timedatectl      Local time: Mon 2016-05-09 21:38:18 NZST  Universal time: Mon 2016-05-09 09:38:18 UTC        RTC time: Mon 2016-05-09 09:38:18       Time zone: Pacific/Auckland (NZST, +1200) Network time on: yesNTP synchronized: yes RTC in local TZ: no
And Java environment:
kinow:~/Development/java/jena/jena$ mvn -vApache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-11T05:41:47+13:00)Maven home: /opt/mavenJava version: 1.8.0_91, vendor: Oracle CorporationJava home: /usr/lib/jvm/java-8-oracle/jreDefault locale: en_NZ, platform encoding: UTF-8OS name: "linux", version: "4.4.0-22-generic", arch: "amd64", family: "unix"
(Ubuntu 16.04 + Java 8 + Maven 3)
CheersBruno
 
      From: Andy Seaborne <an...@apache.org>
 To: dev@jena.apache.org 
 Sent: Thursday, 5 May 2016 7:53 AM
 Subject: [VOTE] Release Jena 3.1.0 (2nd proposed candidate)
   
Hi,

Here is a vote on a release of Jena 3.1.0
(with Fuseki 2.4.0 and Fuseki 1.4.0).

This is the second proposed candidate for this release.

This fixes, from the previous proposed candidate
1/ Presence of binaries in the source-release
2/ Jump in large size of binary downloads due to javadoc inclusion

* Dependency changes:

Upgrades:
  jsonld-java : 2.8.2
  jackson 2.6.3
  slf4j 1.7.20
  dexx collections 0.6

Key features listed below.

Everyone, not just committers, is invited to test and vote.

Staging repository:
https://repository.apache.org/content/repositories/orgapachejena-1012/

Proposed dist/ area:
    https://dist.apache.org/repos/dist/dev/jena/

Keys:
    https://svn.apache.org/repos/asf/jena/dist/KEYS

Git commit (browser URL):
    http://git-wip-us.apache.org/repos/asf/jena/commit/e7ee6bb6

Git Commit Hash:
    e7ee6bb69a5d7ce930a2529dd576a9ea209596a3

Git Commit Tag:
    jena-3.1.0-rc3

Please vote to approve this release:

    [ ] +1 Approve the release
    [ ]  0 Don't care
    [ ] -1 Don't release, because ...

This vote will be open to at least

      7th May 2016, 23:59 UTC

If you expect to check the release but the 72 hour limit does not work 
for you, please email within the schedule above with an expected time 
and we can extend the vote period.

Thanks,

    Andy

Checking needed:

+ does everything work on Linux?
+ does everything work on MS Windows?
+ does everything work on OS X?
+ are the GPG signatures fine?
+ are the checksums correct?
+ is there a source archive?
+ can the source archive really be built?
+ is there a correct LICENSE and NOTICE file in each artifact
      (both source and binary artifacts)?
+ does the NOTICE file contain all necessary attributions?
+ have any licenses of dependencies changed due to upgrades?
        if so have LICENSE and NOTICE been upgraded appropriately?
+ does the tag/commit in the SCM contain reproducible sources?


---------------------------

Key features of the release:

* In-memory txn dataset (Adam Soroka) (RC in 3.0.1)

http://jena.staging.apache.org/documentation/rdf/datasets.html

* Quads (Qihong Lin) (RC in 3.0.1)

http://jena.staging.apache.org/documentation/query/construct-quad.html

* DatasetGraphs & transactions integration

* Alternative QueryParsers in jena-text

* new module jena-cmds
"jena.*"

* Fuseki: Multiple service per file, shared datasets

* Logging
log4j marked <optional>

* New custom functions and aggregate functions
Added:
* afn:springf (contribution from Alessandro Seganti)
* The XQuery/XPath Functions and Operators "math:" functions
* Custom aggregates for stdev etc. (also STDEV etc as keywords).

* FactoryRDF
Parsing RDF now saves space by interning RDFTerms created
during a each parser run.

* OSGi fixes (Jaroslav Pullmann)

* General maintenance: about 80 JIRA.

[CANCELLED] [VOTE] Release Jena 3.1.0 (2nd proposed candidate)

Posted by Andy Seaborne <an...@apache.org>.

Things to be fixed:

java-jsonld : revert to 0.7.0 for this Jena release
OSGi : include optional dependency on 3rd party bundle for Xerces

     Andy