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 2017/10/30 11:20:54 UTC
[VOTE] Release Apache Jena 3.5.0 (RC2)
Hi,
Here is a vote on a release of Jena 3.5.0.
This is the second proposed candidate for a 3.5.0 release.
Note - the deadline is 18:00 UTC on Thursday - not midnight - so that
bytes can be pushed out and sync over night.
==== Release changes
Introducing TDB2:
http://jena.staging.apache.org/documentation/tdb2/
*TDB2 is not compatible with TDB1*
Compared to TDB1:
* No size limits on transactions : bulk uploads into a live Fuseki
can be 100's of millions of triples.
* Models and Graphs can be passed across transactions
* No queue of delayed updates, no transaction backlog problems.
* "Writer pays" - readers don't
All work for update is done on the writer thread.
* Datatypes of numerics preserved; xsd:doubles supported.
TDB2 is subject to change.
We solicit any and all feedback (good and bad!) about TDB2 to help
advance it to deployment-ready.
JENA-1390 : Add StmtIterator.toModel :
JENA-1392 : Add dynamic dataset support to SDB.
JENA-1395 : "--output RDF/XML" now prints using the basic block-oriented
writer, which uses less memory. Use "--formatted" (same as "--pretty")
for pretty printed RDF/XML.
JENA-1398 :
Upgrade FOAF to add new spelling and deprecation of old for archaic FOAF
properties
== Dependency changes:
No license changes.
Upgrade jsonld-java to 0.11
jackson to 2.9.0
commons-fileuploader to 1.3.2->1.3.3
commons-io 2.5 in jena-base
(was pulled in anyway by jsonld-java)
==== Release Vote
Everyone, not just committers, is invited to test and vote.
Please download and test the proposed release.
Staging repository:
https://repository.apache.org/content/repositories/orgapachejena-1020/
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/665bad4f
Git Commit Hash:
665bad4f2ea1d2fe5e0fe13f1ae7b1006afc8009
Git Commit Tag:
jena-3.5.0-rc2
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
Thursday, 2017-11-02, 18:00 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?
(NB This requires a "mvn install" first time)
+ 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?
[RESULT] [VOTE] Release Apache Jena 3.5.0 (RC2)
Posted by Andy Seaborne <an...@apache.org>.
This vote passes with 4 +1's:
Andy, Bruno, Osma, Adam
Thansk for all the work to improve the testing.
I'll push the bytes out and send a [ANN] to users@ soon. Please tweet
the link etc etc.
All being well, I'll send something out to the general semweb list as
well after a few days.
Andy
On 30/10/17 11:20, Andy Seaborne wrote:
> Hi,
>
> Here is a vote on a release of Jena 3.5.0.
>
> This is the second proposed candidate for a 3.5.0 release.
>
> Note - the deadline is 18:00 UTC on Thursday - not midnight - so that
> bytes can be pushed out and sync over night.
>
>
> ==== Release changes
>
> Introducing TDB2:
> http://jena.staging.apache.org/documentation/tdb2/
>
> *TDB2 is not compatible with TDB1*
>
> Compared to TDB1:
> * No size limits on transactions : bulk uploads into a live Fuseki
> can be 100's of millions of triples.
> * Models and Graphs can be passed across transactions
> * No queue of delayed updates, no transaction backlog problems.
> * "Writer pays" - readers don't
> All work for update is done on the writer thread.
> * Datatypes of numerics preserved; xsd:doubles supported.
>
> TDB2 is subject to change.
>
> We solicit any and all feedback (good and bad!) about TDB2 to help
> advance it to deployment-ready.
>
>
> JENA-1390 : Add StmtIterator.toModel :
>
> JENA-1392 : Add dynamic dataset support to SDB.
>
> JENA-1395 : "--output RDF/XML" now prints using the basic block-oriented
> writer, which uses less memory. Use "--formatted" (same as "--pretty")
> for pretty printed RDF/XML.
>
> JENA-1398 :
> Upgrade FOAF to add new spelling and deprecation of old for archaic FOAF
> properties
>
> == Dependency changes:
>
> No license changes.
>
> Upgrade jsonld-java to 0.11
> jackson to 2.9.0
> commons-fileuploader to 1.3.2->1.3.3
> commons-io 2.5 in jena-base
> (was pulled in anyway by jsonld-java)
>
> ==== Release Vote
>
> Everyone, not just committers, is invited to test and vote.
> Please download and test the proposed release.
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachejena-1020/
>
> 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/665bad4f
>
> Git Commit Hash:
> 665bad4f2ea1d2fe5e0fe13f1ae7b1006afc8009
>
> Git Commit Tag:
> jena-3.5.0-rc2
>
> 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
>
> Thursday, 2017-11-02, 18:00 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?
> (NB This requires a "mvn install" first time)
> + 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?
Re: [] Release Apache Jena 3.5.0 (RC2)
Posted by Osma Suominen <os...@helsinki.fi>.
Andy Seaborne kirjoitti 30.10.2017 klo 16:01:
> Hi Osma,
>
> I think you've identified the "group id" gotcha.
I did a PR on this (JENA-1411 / PR #300).
> I can't tell if the elasticsearch test failure is one of it's "usual
> ones" (it's erratic on Jenkins).
I think the ES issue may be due to high load, as you say below. I have a
HDD on this machine and running the build makes everything painfully
slow. ES can be slow to start even in much better circumstances (on my
laptop with SSD it takes several seconds to boot up).
> BaseESTest.POST is 9500, direct transport.
>
> What should it be?
This is OK. It's different from the default ES ports (9200, 9300).
> Yes - elasticsearch testing does fail intermittently sometimes. Theer
> are variations on this happening occasionally on Jenkins when it is busy
> (scheduling >1 build per slave machine).
Maybe simply upping the 30 second timeout would help. It can be
specified in the jena-text-es/pom.xml configuration for
elasticsearch-maven-plugin, the same place where transportPort and
httpPort are set, like this:
<timeout>60</timeout>
I can test this on my HDD machine. So far it's failed for me twice and
worked maybe four times, so with the current timeout of 30 second, it
seems to fail maybe one third of the time.
-Osma
--
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
Re: [] Release Apache Jena 3.5.0 (RC2)
Posted by Andy Seaborne <an...@apache.org>.
Hi Osma,
I think you've identified the "group id" gotcha.
I can't tell if the elasticsearch test failure is one of it's "usual
ones" (it's erratic on Jenkins).
More inline:
On 30/10/17 12:50, Osma Suominen wrote:
> Thanks for preparing the second RC Andy! Excellent work, and very
> timely, considering that several problems were found with the RC1 build
> late last week and you got all fixes integrated already!
>
> I tried to build RC2 on two different Ubuntu 16.04 machines. They have
> slightly different Java and Maven versions.
>
>
> On one machine the build (using "mvn clean install") went fine. Maven
> 3.3.9, Java 1.8.0_131 (OpenJDK).
>
> On the other (Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
> 2015-11-10T18:41:47+02:00), Java 1.8.0_151 / Oracle) I first got this:
>
> [INFO] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 07:48 min
> [INFO] Finished at: 2017-10-30T13:53:07+02:00
> [INFO] Final Memory: 101M/829M
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] Failed to execute goal
> com.github.alexcojocaru:elasticsearch-maven-plugin:5.2:runforked
> (start-elasticsearch) on project jena-text-es: Condition returned by
> method "waitToStart" in class
> com.github.alexcojocaru.mojo.elasticsearch.v2.client.Monitor was not
> fulfilled within 30 seconds. -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the
> -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR] mvn <goals> -rf :jena-text-es
> [INFO] Stopping the Elasticsearch process at application shutdown ...
> [INFO] ... the Elasticsearch process has stopped. Exit code: 143
> [INFO] Elasticsearch [0] stopped with exit code 143
>
>
> So apparently Elasticsearch didn't start properly for the jena-text-es
> integration tests. I happen to have Elasticsearch running on this
> machine but IIRC the tests should use a non-standard TCP port, so the
> two Elasticsearch instances shouldn't interfer with each other.
BaseESTest.POST is 9500, direct transport.
What should it be?
>
> I just resumed the build without doing anything else, and it worked the
> second time, so maybe it was just a random transient error.
Yes - elasticsearch testing does fail intermittently sometimes. Theer
are variations on this happening occasionally on Jenkins when it is busy
(scheduling >1 build per slave machine).
> But then I
> got this:
>
>
> [INFO] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 02:20 min
> [INFO] Finished at: 2017-10-30T14:25:55+02:00
> [INFO] Final Memory: 89M/788M
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-assembly-plugin:2.6:single
> (create-zip-assembly) on project apache-jena-fuseki: Execution
> create-zip-assembly of goal
> org.apache.maven.plugins:maven-assembly-plugin:2.6:single failed: group
> id '3000000' is too big ( > 2097151 ). Use STAR or POSIX extensions to
> overcome this limit -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the
> -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR] mvn <goals> -rf :apache-jena-fuseki
> [INFO] The Elasticsearch process has already stopped. Nothing to clean up
>
> According to the error above, as well as [1], this can be fixed by using
> POSIX tar format.
>
> I think this happens because on this machine (administered by my
> employer, University of Helsinki, with LDAP authentication) my user
> account has a high group ID (3000000), while the other machine is a
> personal laptop where I've installed Ubuntu myself and my group ID is 1000.
>
> I can try to fix this in a PR,
Great.
>but I don't think it's release critical.
> It's probably not a new issue, I just haven't done a full Jena build on
> this machine, at least not after it was reinstalled some months ago.
>
> -Osma
>
> [1]
> https://maven.apache.org/plugins/maven-assembly-plugin/faq.html#tarFileModes
>
>
>
> Andy Seaborne kirjoitti 30.10.2017 klo 13:20:
>> Hi,
>>
>> Here is a vote on a release of Jena 3.5.0.
>>
>> This is the second proposed candidate for a 3.5.0 release.
>>
>> Note - the deadline is 18:00 UTC on Thursday - not midnight - so that
>> bytes can be pushed out and sync over night.
>>
>>
>> ==== Release changes
>>
>> Introducing TDB2:
>> http://jena.staging.apache.org/documentation/tdb2/
>>
>> *TDB2 is not compatible with TDB1*
>>
>> Compared to TDB1:
>> * No size limits on transactions : bulk uploads into a live Fuseki
>> can be 100's of millions of triples.
>> * Models and Graphs can be passed across transactions
>> * No queue of delayed updates, no transaction backlog problems.
>> * "Writer pays" - readers don't
>> All work for update is done on the writer thread.
>> * Datatypes of numerics preserved; xsd:doubles supported.
>>
>> TDB2 is subject to change.
>>
>> We solicit any and all feedback (good and bad!) about TDB2 to help
>> advance it to deployment-ready.
>>
>>
>> JENA-1390 : Add StmtIterator.toModel :
>>
>> JENA-1392 : Add dynamic dataset support to SDB.
>>
>> JENA-1395 : "--output RDF/XML" now prints using the basic
>> block-oriented writer, which uses less memory. Use "--formatted"
>> (same as "--pretty") for pretty printed RDF/XML.
>>
>> JENA-1398 :
>> Upgrade FOAF to add new spelling and deprecation of old for archaic
>> FOAF properties
>>
>> == Dependency changes:
>>
>> No license changes.
>>
>> Upgrade jsonld-java to 0.11
>> jackson to 2.9.0
>> commons-fileuploader to 1.3.2->1.3.3
>> commons-io 2.5 in jena-base
>> (was pulled in anyway by jsonld-java)
>>
>> ==== Release Vote
>>
>> Everyone, not just committers, is invited to test and vote.
>> Please download and test the proposed release.
>>
>> Staging repository:
>> https://repository.apache.org/content/repositories/orgapachejena-1020/
>>
>> 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/665bad4f
>>
>> Git Commit Hash:
>> 665bad4f2ea1d2fe5e0fe13f1ae7b1006afc8009
>>
>> Git Commit Tag:
>> jena-3.5.0-rc2
>>
>> 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
>>
>> Thursday, 2017-11-02, 18:00 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?
>> (NB This requires a "mvn install" first time)
>> + 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?
>
>
Re: [VOTE] Release Apache Jena 3.5.0 (RC2)
Posted by aj...@apache.org.
Yeah, I was somehow missing your key. Weird, I thought I had imported it a long time ago. Oh, well, all good on that front.
+1 to the release.
ajs6f
Andy Seaborne wrote on 10/30/17 10:34 AM:
>
>
> On 30/10/17 14:04, ajs6f@apache.org wrote:
>> I got a clean build with Mac OS X, Maven 3.5.0, Java version: 1.8.0_65, vendor: Oracle Corporation.
>>
>> However, when checking the sigs, I'm getting:
>>
>> ➜ /tmp gpg --verify apache-jena-3.5.0.tar.gz.asc apache-jena-3.5.0.tar.gz
>> gpg: Signature made Mon Oct 30 05:47:51 2017 EDT
>> gpg: using RSA key 04C95136D236A58F
>> gpg: Can't check signature: No public key
>>
>> And I can't find a sig with that string in the MIT keyserver... Andy, did you change keys recently?
>
> Not for a while.
>
> Search for "seaborne" and I see
>
> pub 4096R/D236A58F 2016-11-04 Andy Seaborne (Code signing key) <an...@apache.org>
>
> and link to:
>
> https://pgp.mit.edu/pks/lookup?op=get&search=0x04C95136D236A58F
>
> and the public key is in the KEYS file.
>
> gpg --import KEYS
> pgp < KEYS
>
> Andy
>
>>
>> ajs6f
>>
>> Osma Suominen wrote on 10/30/17 8:50 AM:
>>> Thanks for preparing the second RC Andy! Excellent work, and very timely, considering that several problems were found
>>> with the RC1 build late last week and you got all fixes integrated already!
>>>
>>> I tried to build RC2 on two different Ubuntu 16.04 machines. They have slightly different Java and Maven versions.
>>>
>>>
>>> On one machine the build (using "mvn clean install") went fine. Maven 3.3.9, Java 1.8.0_131 (OpenJDK).
>>>
>>> On the other (Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T18:41:47+02:00), Java 1.8.0_151 /
>>> Oracle) I first got this:
>>>
>>> [INFO] BUILD FAILURE
>>> [INFO] ------------------------------------------------------------------------
>>> [INFO] Total time: 07:48 min
>>> [INFO] Finished at: 2017-10-30T13:53:07+02:00
>>> [INFO] Final Memory: 101M/829M
>>> [INFO] ------------------------------------------------------------------------
>>> [ERROR] Failed to execute goal com.github.alexcojocaru:elasticsearch-maven-plugin:5.2:runforked (start-elasticsearch) on
>>> project jena-text-es: Condition returned by method "waitToStart" in class
>>> com.github.alexcojocaru.mojo.elasticsearch.v2.client.Monitor was not fulfilled within 30 seconds. -> [Help 1]
>>> [ERROR]
>>> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
>>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>>> [ERROR]
>>> [ERROR] For more information about the errors and possible solutions, please read the following articles:
>>> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
>>> [ERROR]
>>> [ERROR] After correcting the problems, you can resume the build with the command
>>> [ERROR] mvn <goals> -rf :jena-text-es
>>> [INFO] Stopping the Elasticsearch process at application shutdown ...
>>> [INFO] ... the Elasticsearch process has stopped. Exit code: 143
>>> [INFO] Elasticsearch [0] stopped with exit code 143
>>>
>>>
>>> So apparently Elasticsearch didn't start properly for the jena-text-es integration tests. I happen to have Elasticsearch
>>> running on this machine but IIRC the tests should use a non-standard TCP port, so the two Elasticsearch instances
>>> shouldn't interfer with each other.
>>>
>>> I just resumed the build without doing anything else, and it worked the second time, so maybe it was just a random
>>> transient error. But then I got this:
>>>
>>>
>>> [INFO] BUILD FAILURE
>>> [INFO] ------------------------------------------------------------------------
>>> [INFO] Total time: 02:20 min
>>> [INFO] Finished at: 2017-10-30T14:25:55+02:00
>>> [INFO] Final Memory: 89M/788M
>>> [INFO] ------------------------------------------------------------------------
>>> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-assembly-plugin:2.6:single (create-zip-assembly) on
>>> project apache-jena-fuseki: Execution create-zip-assembly of goal
>>> org.apache.maven.plugins:maven-assembly-plugin:2.6:single failed: group id '3000000' is too big ( > 2097151 ). Use STAR
>>> or POSIX extensions to overcome this limit -> [Help 1]
>>> [ERROR]
>>> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
>>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>>> [ERROR]
>>> [ERROR] For more information about the errors and possible solutions, please read the following articles:
>>> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
>>> [ERROR]
>>> [ERROR] After correcting the problems, you can resume the build with the command
>>> [ERROR] mvn <goals> -rf :apache-jena-fuseki
>>> [INFO] The Elasticsearch process has already stopped. Nothing to clean up
>>>
>>> According to the error above, as well as [1], this can be fixed by using POSIX tar format.
>>>
>>> I think this happens because on this machine (administered by my employer, University of Helsinki, with LDAP
>>> authentication) my user account has a high group ID (3000000), while the other machine is a personal laptop where I've
>>> installed Ubuntu myself and my group ID is 1000.
>>>
>>> I can try to fix this in a PR, but I don't think it's release critical. It's probably not a new issue, I just haven't
>>> done a full Jena build on this machine, at least not after it was reinstalled some months ago.
>>>
>>> -Osma
>>>
>>> [1] https://maven.apache.org/plugins/maven-assembly-plugin/faq.html#tarFileModes
>>>
>>>
>>> Andy Seaborne kirjoitti 30.10.2017 klo 13:20:
>>>> Hi,
>>>>
>>>> Here is a vote on a release of Jena 3.5.0.
>>>>
>>>> This is the second proposed candidate for a 3.5.0 release.
>>>>
>>>> Note - the deadline is 18:00 UTC on Thursday - not midnight - so that bytes can be pushed out and sync over night.
>>>>
>>>>
>>>> ==== Release changes
>>>>
>>>> Introducing TDB2:
>>>> http://jena.staging.apache.org/documentation/tdb2/
>>>>
>>>> *TDB2 is not compatible with TDB1*
>>>>
>>>> Compared to TDB1:
>>>> * No size limits on transactions : bulk uploads into a live Fuseki
>>>> can be 100's of millions of triples.
>>>> * Models and Graphs can be passed across transactions
>>>> * No queue of delayed updates, no transaction backlog problems.
>>>> * "Writer pays" - readers don't
>>>> All work for update is done on the writer thread.
>>>> * Datatypes of numerics preserved; xsd:doubles supported.
>>>>
>>>> TDB2 is subject to change.
>>>>
>>>> We solicit any and all feedback (good and bad!) about TDB2 to help advance it to deployment-ready.
>>>>
>>>>
>>>> JENA-1390 : Add StmtIterator.toModel :
>>>>
>>>> JENA-1392 : Add dynamic dataset support to SDB.
>>>>
>>>> JENA-1395 : "--output RDF/XML" now prints using the basic block-oriented writer, which uses less memory. Use
>>>> "--formatted" (same as "--pretty") for pretty printed RDF/XML.
>>>>
>>>> JENA-1398 :
>>>> Upgrade FOAF to add new spelling and deprecation of old for archaic FOAF properties
>>>>
>>>> == Dependency changes:
>>>>
>>>> No license changes.
>>>>
>>>> Upgrade jsonld-java to 0.11
>>>> jackson to 2.9.0
>>>> commons-fileuploader to 1.3.2->1.3.3
>>>> commons-io 2.5 in jena-base
>>>> (was pulled in anyway by jsonld-java)
>>>>
>>>> ==== Release Vote
>>>>
>>>> Everyone, not just committers, is invited to test and vote.
>>>> Please download and test the proposed release.
>>>>
>>>> Staging repository:
>>>> https://repository.apache.org/content/repositories/orgapachejena-1020/
>>>>
>>>> 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/665bad4f
>>>>
>>>> Git Commit Hash:
>>>> 665bad4f2ea1d2fe5e0fe13f1ae7b1006afc8009
>>>>
>>>> Git Commit Tag:
>>>> jena-3.5.0-rc2
>>>>
>>>> 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
>>>>
>>>> Thursday, 2017-11-02, 18:00 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?
>>>> (NB This requires a "mvn install" first time)
>>>> + 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?
>>>
>>>
Re: [] Release Apache Jena 3.5.0 (RC2)
Posted by Andy Seaborne <an...@apache.org>.
On 30/10/17 14:04, ajs6f@apache.org wrote:
> I got a clean build with Mac OS X, Maven 3.5.0, Java version: 1.8.0_65,
> vendor: Oracle Corporation.
>
> However, when checking the sigs, I'm getting:
>
> ➜ /tmp gpg --verify apache-jena-3.5.0.tar.gz.asc apache-jena-3.5.0.tar.gz
> gpg: Signature made Mon Oct 30 05:47:51 2017 EDT
> gpg: using RSA key 04C95136D236A58F
> gpg: Can't check signature: No public key
>
> And I can't find a sig with that string in the MIT keyserver... Andy,
> did you change keys recently?
Not for a while.
Search for "seaborne" and I see
pub 4096R/D236A58F 2016-11-04 Andy Seaborne (Code signing key)
<an...@apache.org>
and link to:
https://pgp.mit.edu/pks/lookup?op=get&search=0x04C95136D236A58F
and the public key is in the KEYS file.
gpg --import KEYS
pgp < KEYS
Andy
>
> ajs6f
>
> Osma Suominen wrote on 10/30/17 8:50 AM:
>> Thanks for preparing the second RC Andy! Excellent work, and very
>> timely, considering that several problems were found
>> with the RC1 build late last week and you got all fixes integrated
>> already!
>>
>> I tried to build RC2 on two different Ubuntu 16.04 machines. They have
>> slightly different Java and Maven versions.
>>
>>
>> On one machine the build (using "mvn clean install") went fine. Maven
>> 3.3.9, Java 1.8.0_131 (OpenJDK).
>>
>> On the other (Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
>> 2015-11-10T18:41:47+02:00), Java 1.8.0_151 /
>> Oracle) I first got this:
>>
>> [INFO] BUILD FAILURE
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Total time: 07:48 min
>> [INFO] Finished at: 2017-10-30T13:53:07+02:00
>> [INFO] Final Memory: 101M/829M
>> [INFO]
>> ------------------------------------------------------------------------
>> [ERROR] Failed to execute goal
>> com.github.alexcojocaru:elasticsearch-maven-plugin:5.2:runforked
>> (start-elasticsearch) on
>> project jena-text-es: Condition returned by method "waitToStart" in class
>> com.github.alexcojocaru.mojo.elasticsearch.v2.client.Monitor was not
>> fulfilled within 30 seconds. -> [Help 1]
>> [ERROR]
>> [ERROR] To see the full stack trace of the errors, re-run Maven with
>> the -e switch.
>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>> [ERROR]
>> [ERROR] For more information about the errors and possible solutions,
>> please read the following articles:
>> [ERROR] [Help 1]
>> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
>> [ERROR]
>> [ERROR] After correcting the problems, you can resume the build with
>> the command
>> [ERROR] mvn <goals> -rf :jena-text-es
>> [INFO] Stopping the Elasticsearch process at application shutdown ...
>> [INFO] ... the Elasticsearch process has stopped. Exit code: 143
>> [INFO] Elasticsearch [0] stopped with exit code 143
>>
>>
>> So apparently Elasticsearch didn't start properly for the jena-text-es
>> integration tests. I happen to have Elasticsearch
>> running on this machine but IIRC the tests should use a non-standard
>> TCP port, so the two Elasticsearch instances
>> shouldn't interfer with each other.
>>
>> I just resumed the build without doing anything else, and it worked
>> the second time, so maybe it was just a random
>> transient error. But then I got this:
>>
>>
>> [INFO] BUILD FAILURE
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Total time: 02:20 min
>> [INFO] Finished at: 2017-10-30T14:25:55+02:00
>> [INFO] Final Memory: 89M/788M
>> [INFO]
>> ------------------------------------------------------------------------
>> [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-assembly-plugin:2.6:single
>> (create-zip-assembly) on
>> project apache-jena-fuseki: Execution create-zip-assembly of goal
>> org.apache.maven.plugins:maven-assembly-plugin:2.6:single failed:
>> group id '3000000' is too big ( > 2097151 ). Use STAR
>> or POSIX extensions to overcome this limit -> [Help 1]
>> [ERROR]
>> [ERROR] To see the full stack trace of the errors, re-run Maven with
>> the -e switch.
>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>> [ERROR]
>> [ERROR] For more information about the errors and possible solutions,
>> please read the following articles:
>> [ERROR] [Help 1]
>> http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
>> [ERROR]
>> [ERROR] After correcting the problems, you can resume the build with
>> the command
>> [ERROR] mvn <goals> -rf :apache-jena-fuseki
>> [INFO] The Elasticsearch process has already stopped. Nothing to clean up
>>
>> According to the error above, as well as [1], this can be fixed by
>> using POSIX tar format.
>>
>> I think this happens because on this machine (administered by my
>> employer, University of Helsinki, with LDAP
>> authentication) my user account has a high group ID (3000000), while
>> the other machine is a personal laptop where I've
>> installed Ubuntu myself and my group ID is 1000.
>>
>> I can try to fix this in a PR, but I don't think it's release
>> critical. It's probably not a new issue, I just haven't
>> done a full Jena build on this machine, at least not after it was
>> reinstalled some months ago.
>>
>> -Osma
>>
>> [1]
>> https://maven.apache.org/plugins/maven-assembly-plugin/faq.html#tarFileModes
>>
>>
>>
>> Andy Seaborne kirjoitti 30.10.2017 klo 13:20:
>>> Hi,
>>>
>>> Here is a vote on a release of Jena 3.5.0.
>>>
>>> This is the second proposed candidate for a 3.5.0 release.
>>>
>>> Note - the deadline is 18:00 UTC on Thursday - not midnight - so that
>>> bytes can be pushed out and sync over night.
>>>
>>>
>>> ==== Release changes
>>>
>>> Introducing TDB2:
>>> http://jena.staging.apache.org/documentation/tdb2/
>>>
>>> *TDB2 is not compatible with TDB1*
>>>
>>> Compared to TDB1:
>>> * No size limits on transactions : bulk uploads into a live Fuseki
>>> can be 100's of millions of triples.
>>> * Models and Graphs can be passed across transactions
>>> * No queue of delayed updates, no transaction backlog problems.
>>> * "Writer pays" - readers don't
>>> All work for update is done on the writer thread.
>>> * Datatypes of numerics preserved; xsd:doubles supported.
>>>
>>> TDB2 is subject to change.
>>>
>>> We solicit any and all feedback (good and bad!) about TDB2 to help
>>> advance it to deployment-ready.
>>>
>>>
>>> JENA-1390 : Add StmtIterator.toModel :
>>>
>>> JENA-1392 : Add dynamic dataset support to SDB.
>>>
>>> JENA-1395 : "--output RDF/XML" now prints using the basic
>>> block-oriented writer, which uses less memory. Use
>>> "--formatted" (same as "--pretty") for pretty printed RDF/XML.
>>>
>>> JENA-1398 :
>>> Upgrade FOAF to add new spelling and deprecation of old for archaic
>>> FOAF properties
>>>
>>> == Dependency changes:
>>>
>>> No license changes.
>>>
>>> Upgrade jsonld-java to 0.11
>>> jackson to 2.9.0
>>> commons-fileuploader to 1.3.2->1.3.3
>>> commons-io 2.5 in jena-base
>>> (was pulled in anyway by jsonld-java)
>>>
>>> ==== Release Vote
>>>
>>> Everyone, not just committers, is invited to test and vote.
>>> Please download and test the proposed release.
>>>
>>> Staging repository:
>>>
>>> https://repository.apache.org/content/repositories/orgapachejena-1020/
>>>
>>> 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/665bad4f
>>>
>>> Git Commit Hash:
>>> 665bad4f2ea1d2fe5e0fe13f1ae7b1006afc8009
>>>
>>> Git Commit Tag:
>>> jena-3.5.0-rc2
>>>
>>> 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
>>>
>>> Thursday, 2017-11-02, 18:00 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?
>>> (NB This requires a "mvn install" first time)
>>> + 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?
>>
>>
Re: [] Release Apache Jena 3.5.0 (RC2)
Posted by aj...@apache.org.
I got a clean build with Mac OS X, Maven 3.5.0, Java version: 1.8.0_65, vendor: Oracle Corporation.
However, when checking the sigs, I'm getting:
➜ /tmp gpg --verify apache-jena-3.5.0.tar.gz.asc apache-jena-3.5.0.tar.gz
gpg: Signature made Mon Oct 30 05:47:51 2017 EDT
gpg: using RSA key 04C95136D236A58F
gpg: Can't check signature: No public key
And I can't find a sig with that string in the MIT keyserver... Andy, did you change keys recently?
ajs6f
Osma Suominen wrote on 10/30/17 8:50 AM:
> Thanks for preparing the second RC Andy! Excellent work, and very timely, considering that several problems were found
> with the RC1 build late last week and you got all fixes integrated already!
>
> I tried to build RC2 on two different Ubuntu 16.04 machines. They have slightly different Java and Maven versions.
>
>
> On one machine the build (using "mvn clean install") went fine. Maven 3.3.9, Java 1.8.0_131 (OpenJDK).
>
> On the other (Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T18:41:47+02:00), Java 1.8.0_151 /
> Oracle) I first got this:
>
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 07:48 min
> [INFO] Finished at: 2017-10-30T13:53:07+02:00
> [INFO] Final Memory: 101M/829M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal com.github.alexcojocaru:elasticsearch-maven-plugin:5.2:runforked (start-elasticsearch) on
> project jena-text-es: Condition returned by method "waitToStart" in class
> com.github.alexcojocaru.mojo.elasticsearch.v2.client.Monitor was not fulfilled within 30 seconds. -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the command
> [ERROR] mvn <goals> -rf :jena-text-es
> [INFO] Stopping the Elasticsearch process at application shutdown ...
> [INFO] ... the Elasticsearch process has stopped. Exit code: 143
> [INFO] Elasticsearch [0] stopped with exit code 143
>
>
> So apparently Elasticsearch didn't start properly for the jena-text-es integration tests. I happen to have Elasticsearch
> running on this machine but IIRC the tests should use a non-standard TCP port, so the two Elasticsearch instances
> shouldn't interfer with each other.
>
> I just resumed the build without doing anything else, and it worked the second time, so maybe it was just a random
> transient error. But then I got this:
>
>
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 02:20 min
> [INFO] Finished at: 2017-10-30T14:25:55+02:00
> [INFO] Final Memory: 89M/788M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-assembly-plugin:2.6:single (create-zip-assembly) on
> project apache-jena-fuseki: Execution create-zip-assembly of goal
> org.apache.maven.plugins:maven-assembly-plugin:2.6:single failed: group id '3000000' is too big ( > 2097151 ). Use STAR
> or POSIX extensions to overcome this limit -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the command
> [ERROR] mvn <goals> -rf :apache-jena-fuseki
> [INFO] The Elasticsearch process has already stopped. Nothing to clean up
>
> According to the error above, as well as [1], this can be fixed by using POSIX tar format.
>
> I think this happens because on this machine (administered by my employer, University of Helsinki, with LDAP
> authentication) my user account has a high group ID (3000000), while the other machine is a personal laptop where I've
> installed Ubuntu myself and my group ID is 1000.
>
> I can try to fix this in a PR, but I don't think it's release critical. It's probably not a new issue, I just haven't
> done a full Jena build on this machine, at least not after it was reinstalled some months ago.
>
> -Osma
>
> [1] https://maven.apache.org/plugins/maven-assembly-plugin/faq.html#tarFileModes
>
>
> Andy Seaborne kirjoitti 30.10.2017 klo 13:20:
>> Hi,
>>
>> Here is a vote on a release of Jena 3.5.0.
>>
>> This is the second proposed candidate for a 3.5.0 release.
>>
>> Note - the deadline is 18:00 UTC on Thursday - not midnight - so that bytes can be pushed out and sync over night.
>>
>>
>> ==== Release changes
>>
>> Introducing TDB2:
>> http://jena.staging.apache.org/documentation/tdb2/
>>
>> *TDB2 is not compatible with TDB1*
>>
>> Compared to TDB1:
>> * No size limits on transactions : bulk uploads into a live Fuseki
>> can be 100's of millions of triples.
>> * Models and Graphs can be passed across transactions
>> * No queue of delayed updates, no transaction backlog problems.
>> * "Writer pays" - readers don't
>> All work for update is done on the writer thread.
>> * Datatypes of numerics preserved; xsd:doubles supported.
>>
>> TDB2 is subject to change.
>>
>> We solicit any and all feedback (good and bad!) about TDB2 to help advance it to deployment-ready.
>>
>>
>> JENA-1390 : Add StmtIterator.toModel :
>>
>> JENA-1392 : Add dynamic dataset support to SDB.
>>
>> JENA-1395 : "--output RDF/XML" now prints using the basic block-oriented writer, which uses less memory. Use
>> "--formatted" (same as "--pretty") for pretty printed RDF/XML.
>>
>> JENA-1398 :
>> Upgrade FOAF to add new spelling and deprecation of old for archaic FOAF properties
>>
>> == Dependency changes:
>>
>> No license changes.
>>
>> Upgrade jsonld-java to 0.11
>> jackson to 2.9.0
>> commons-fileuploader to 1.3.2->1.3.3
>> commons-io 2.5 in jena-base
>> (was pulled in anyway by jsonld-java)
>>
>> ==== Release Vote
>>
>> Everyone, not just committers, is invited to test and vote.
>> Please download and test the proposed release.
>>
>> Staging repository:
>> https://repository.apache.org/content/repositories/orgapachejena-1020/
>>
>> 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/665bad4f
>>
>> Git Commit Hash:
>> 665bad4f2ea1d2fe5e0fe13f1ae7b1006afc8009
>>
>> Git Commit Tag:
>> jena-3.5.0-rc2
>>
>> 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
>>
>> Thursday, 2017-11-02, 18:00 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?
>> (NB This requires a "mvn install" first time)
>> + 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?
>
>
Re: [] Release Apache Jena 3.5.0 (RC2)
Posted by Osma Suominen <os...@helsinki.fi>.
Thanks for preparing the second RC Andy! Excellent work, and very
timely, considering that several problems were found with the RC1 build
late last week and you got all fixes integrated already!
I tried to build RC2 on two different Ubuntu 16.04 machines. They have
slightly different Java and Maven versions.
On one machine the build (using "mvn clean install") went fine. Maven
3.3.9, Java 1.8.0_131 (OpenJDK).
On the other (Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
2015-11-10T18:41:47+02:00), Java 1.8.0_151 / Oracle) I first got this:
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 07:48 min
[INFO] Finished at: 2017-10-30T13:53:07+02:00
[INFO] Final Memory: 101M/829M
[INFO]
------------------------------------------------------------------------
[ERROR] Failed to execute goal
com.github.alexcojocaru:elasticsearch-maven-plugin:5.2:runforked
(start-elasticsearch) on project jena-text-es: Condition returned by
method "waitToStart" in class
com.github.alexcojocaru.mojo.elasticsearch.v2.client.Monitor was not
fulfilled within 30 seconds. -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the
-e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the
command
[ERROR] mvn <goals> -rf :jena-text-es
[INFO] Stopping the Elasticsearch process at application shutdown ...
[INFO] ... the Elasticsearch process has stopped. Exit code: 143
[INFO] Elasticsearch [0] stopped with exit code 143
So apparently Elasticsearch didn't start properly for the jena-text-es
integration tests. I happen to have Elasticsearch running on this
machine but IIRC the tests should use a non-standard TCP port, so the
two Elasticsearch instances shouldn't interfer with each other.
I just resumed the build without doing anything else, and it worked the
second time, so maybe it was just a random transient error. But then I
got this:
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 02:20 min
[INFO] Finished at: 2017-10-30T14:25:55+02:00
[INFO] Final Memory: 89M/788M
[INFO]
------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-assembly-plugin:2.6:single
(create-zip-assembly) on project apache-jena-fuseki: Execution
create-zip-assembly of goal
org.apache.maven.plugins:maven-assembly-plugin:2.6:single failed: group
id '3000000' is too big ( > 2097151 ). Use STAR or POSIX extensions to
overcome this limit -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the
-e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the
command
[ERROR] mvn <goals> -rf :apache-jena-fuseki
[INFO] The Elasticsearch process has already stopped. Nothing to clean up
According to the error above, as well as [1], this can be fixed by using
POSIX tar format.
I think this happens because on this machine (administered by my
employer, University of Helsinki, with LDAP authentication) my user
account has a high group ID (3000000), while the other machine is a
personal laptop where I've installed Ubuntu myself and my group ID is 1000.
I can try to fix this in a PR, but I don't think it's release critical.
It's probably not a new issue, I just haven't done a full Jena build on
this machine, at least not after it was reinstalled some months ago.
-Osma
[1]
https://maven.apache.org/plugins/maven-assembly-plugin/faq.html#tarFileModes
Andy Seaborne kirjoitti 30.10.2017 klo 13:20:
> Hi,
>
> Here is a vote on a release of Jena 3.5.0.
>
> This is the second proposed candidate for a 3.5.0 release.
>
> Note - the deadline is 18:00 UTC on Thursday - not midnight - so that
> bytes can be pushed out and sync over night.
>
>
> ==== Release changes
>
> Introducing TDB2:
> http://jena.staging.apache.org/documentation/tdb2/
>
> *TDB2 is not compatible with TDB1*
>
> Compared to TDB1:
> * No size limits on transactions : bulk uploads into a live Fuseki
> can be 100's of millions of triples.
> * Models and Graphs can be passed across transactions
> * No queue of delayed updates, no transaction backlog problems.
> * "Writer pays" - readers don't
> All work for update is done on the writer thread.
> * Datatypes of numerics preserved; xsd:doubles supported.
>
> TDB2 is subject to change.
>
> We solicit any and all feedback (good and bad!) about TDB2 to help
> advance it to deployment-ready.
>
>
> JENA-1390 : Add StmtIterator.toModel :
>
> JENA-1392 : Add dynamic dataset support to SDB.
>
> JENA-1395 : "--output RDF/XML" now prints using the basic block-oriented
> writer, which uses less memory. Use "--formatted" (same as "--pretty")
> for pretty printed RDF/XML.
>
> JENA-1398 :
> Upgrade FOAF to add new spelling and deprecation of old for archaic FOAF
> properties
>
> == Dependency changes:
>
> No license changes.
>
> Upgrade jsonld-java to 0.11
> jackson to 2.9.0
> commons-fileuploader to 1.3.2->1.3.3
> commons-io 2.5 in jena-base
> (was pulled in anyway by jsonld-java)
>
> ==== Release Vote
>
> Everyone, not just committers, is invited to test and vote.
> Please download and test the proposed release.
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachejena-1020/
>
> 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/665bad4f
>
> Git Commit Hash:
> 665bad4f2ea1d2fe5e0fe13f1ae7b1006afc8009
>
> Git Commit Tag:
> jena-3.5.0-rc2
>
> 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
>
> Thursday, 2017-11-02, 18:00 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?
> (NB This requires a "mvn install" first time)
> + 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?
--
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
Re: [VOTE] Release Apache Jena 3.5.0 (RC2)
Posted by Osma Suominen <os...@helsinki.fi>.
+1
Built on two different Linux machines. I tested RC1 more thoroughly last
week (see my e-mail about TDB2 testing) and I think the results are
still valid since the changes after RC1 were very small.
-Osma
Andy Seaborne kirjoitti 30.10.2017 klo 13:20:
> Hi,
>
> Here is a vote on a release of Jena 3.5.0.
>
> This is the second proposed candidate for a 3.5.0 release.
>
> Note - the deadline is 18:00 UTC on Thursday - not midnight - so that
> bytes can be pushed out and sync over night.
>
>
> ==== Release changes
>
> Introducing TDB2:
> http://jena.staging.apache.org/documentation/tdb2/
>
> *TDB2 is not compatible with TDB1*
>
> Compared to TDB1:
> * No size limits on transactions : bulk uploads into a live Fuseki
> can be 100's of millions of triples.
> * Models and Graphs can be passed across transactions
> * No queue of delayed updates, no transaction backlog problems.
> * "Writer pays" - readers don't
> All work for update is done on the writer thread.
> * Datatypes of numerics preserved; xsd:doubles supported.
>
> TDB2 is subject to change.
>
> We solicit any and all feedback (good and bad!) about TDB2 to help
> advance it to deployment-ready.
>
>
> JENA-1390 : Add StmtIterator.toModel :
>
> JENA-1392 : Add dynamic dataset support to SDB.
>
> JENA-1395 : "--output RDF/XML" now prints using the basic block-oriented
> writer, which uses less memory. Use "--formatted" (same as "--pretty")
> for pretty printed RDF/XML.
>
> JENA-1398 :
> Upgrade FOAF to add new spelling and deprecation of old for archaic FOAF
> properties
>
> == Dependency changes:
>
> No license changes.
>
> Upgrade jsonld-java to 0.11
> jackson to 2.9.0
> commons-fileuploader to 1.3.2->1.3.3
> commons-io 2.5 in jena-base
> (was pulled in anyway by jsonld-java)
>
> ==== Release Vote
>
> Everyone, not just committers, is invited to test and vote.
> Please download and test the proposed release.
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachejena-1020/
>
> 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/665bad4f
>
> Git Commit Hash:
> 665bad4f2ea1d2fe5e0fe13f1ae7b1006afc8009
>
> Git Commit Tag:
> jena-3.5.0-rc2
>
> 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
>
> Thursday, 2017-11-02, 18:00 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?
> (NB This requires a "mvn install" first time)
> + 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?
--
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
Re: [VOTE] Release Apache Jena 3.5.0 (RC2)
Posted by Andy Seaborne <an...@apache.org>.
+1
(tested on Linux)
> 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
>
> Thursday, 2017-11-02, 18:00 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?
> (NB This requires a "mvn install" first time)
> + 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?