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?
