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 2018/03/29 18:28:06 UTC

[VOTE] Apache Jena 3.7.0 RC1

Hi,

Here is a vote on a release of Jena 3.7.0.

This is the first proposed candidate for a 3.7.0 release.

There are process changes.

Deadline:

        2018-04-01 22:00 UTC

April 1st!

==== Process Changes

1/
MD5 files are being discouraged because MD5 is not secure.  Projects are 
now asked to not publish md5.

There are no md5 files in the proposed dist/jena area - files on Apache 
hardware.

There are sha1 and sha512 checksums.
* The sha512 is in Linux sha512sum checkable format.
* The sha1 is whatever maven generated and is the same as will go to 
maven central.

Having the sha1 ties the dist/jena artifacts to maven central (as does 
the .asc).

There are md5 and sha1 in the proposes maven repo staging area for 
sending to maven central. That part of maven is hardwired to md5/sha1 still.

There's a script to setup the sha512.

2/
To establish the proof chain for signed artifacts in /dist/project/, I 
have been asked to try out the new META files.

https://checker.apache.org/doc/README.html#ch-meta

There are two files

/dist/jena/META
/dist/jena/META.asc

META says who signs what, and is itself signed by the PMC chair.

==== Release changes

55 JIRA:
https://s.apache.org/jena-3.7.0-jira

== Significant Changes

** Java9: Building and running on a Java9 platform is supported

JENA-1461 - Allow ARQ custom functions to be written in JavaScript

JENA-1389 - Return `this` rather than `void` from Dataset (API change)
JENA-1495 - Return Model from PrefixMapping methods (API change)

JENA-1458, JENA-1483 - Transaction Promotion

JENA-1453 - Lucene indexes using a graph field are smaller

JENA-1490 - Working with Blank Nodes with Fuseki

== Upgrades to libraries (runtime dependencies):

No dependency changes.

==== Release Vote

Everyone, not just committers, is invited to test and vote.
Please download and test the proposed release.

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

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

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

Git commit (browser URL):
https://git1-us-west.apache.org/repos/asf?p=jena.git;a=commit;h=d4e7063e

Git Commit Hash:
   d4e7063e7a6db8ce77699bd0388e1a1bd6816626

Git Commit Tag:
      jena-3.7.0-rc1

Please vote to approve this release:

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

This vote will be open until at least

        2018-04-01 22:00 UTC

If you expect to check the release but the time 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] Apache Jena 3.7.0 RC1

Posted by Chris Tomlinson <ch...@gmail.com>.

Downloaded https://git1-us-west.apache.org/repos/asf?p=jena.git;a=commit;h=d4e7063e <https://git1-us-west.apache.org/repos/asf?p=jena.git;a=commit;h=d4e7063e>; mvn clean package; and tested by running jena-fuseki-basic on Mac OS X 10.13.3, Oracle jdk 1.8.0_162.

> Please vote to approve this release:
>        [ ] +1 Approve the release
>        [ ]  0 Don't care
>        [ ] -1 Don't release, because ...

+1

> This vote will be open until at least
>        2018-04-01 22:00 UTC


Regards,
Chris

Re: [VOTE] Apache Jena 3.7.0 RC1

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

> Please vote to approve this release:
> 
>         [ ] +1 Approve the release
>         [ ]  0 Don't care
>         [ ] -1 Don't release, because ...

+1

> 
> This vote will be open until at least
> 
>         2018-04-01 22:00 UTC

Re: [] Apache Jena 3.7.0 RC1

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


On 03/04/18 18:15, Andy Seaborne wrote:
> 1/ This is 3.8.0-SNAPSHOT - not the release candidate.
> 
> 2/ Jenkins has been building 3.8.0-SNAPSHOT including javadoc.
> 
> 3/ It says it is in the javadoc plugin:
> 
> """
> org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar failed.:
> NullPointerException -> [Help 1]
> """
> 
> so we have very little control there.
> 
> (-Pdev does not produce javadoc.)
> 
> Best I can suggest is completely clear out the M2 repo of 3.8.0-SNAPSHOT 
> items and retry.
> 
> I will try on my machine when I can. (I am conducting timed runs for the 
> users@ report ATM.)

Works for me:
Code : commit b850a9cd11

Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d; 
2017-10-18T08:58:13+01:00)
Maven home: /home/afs/sys/apache-maven
Java version: 1.8.0_162, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-8-openjdk-amd64/jre
Default locale: en_GB, platform encoding: UTF-8
OS name: "linux", version: "4.13.0-37-generic", arch: "amd64", family: 
"unix"



> 
>      Andy
> 
> On 03/04/18 17:30, Claude Warren wrote:
>> Sorry, should have added:
>>
>> openjdk version "1.8.0_162"
>> OpenJDK Runtime Environment (build 
>> 1.8.0_162-8u162-b12-0ubuntu0.16.04.2-b12)
>> OpenJDK 64-Bit Server VM (build 25.162-b12, mixed mode)
>>
>> Linux claude-XPS-15-9560 4.13.0-37-generic #42~16.04.1-Ubuntu SMP Wed 
>> Mar 7
>> 16:03:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
>>
>>
>>
>>
>> On Tue, Apr 3, 2018 at 5:20 PM, Claude Warren <cl...@xenei.com> wrote:
>>
>>> Compile on Ubuntu with clone from git fails.
>>>
>>> mvn clean install -Pdev
>>>
>>> success
>>>
>>> mvn clean install
>>>
>>> fails with:
>>>
>>> [INFO] --- maven-javadoc-plugin:3.0.0:jar (attach-javadocs) @ 
>>> jena-base ---
>>> [INFO] The goal 
>>> 'org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:javadoc'
>>> has not been previously called for the module: 
>>> 'org.apache.jena:jena-shaded-guava:jar:3.8.0-SNAPSHOT'.
>>> Trying to invoke it...
>>> [WARNING] Creating fake javadoc directory to prevent repeated 
>>> invocations:
>>> /home/claude/git/jena/jena-shaded-guava/target/apidocs
>>> [INFO] ------------------------------------------------------------
>>> ------------
>>> [INFO] Reactor Summary:
>>> [INFO]
>>> [INFO] Apache Jena 3.8.0-SNAPSHOT ......................... SUCCESS [
>>> 1.502 s]
>>> [INFO] Apache Jena - Shadowed external libraries .......... SUCCESS [
>>> 1.545 s]
>>> [INFO] Apache Jena - IRI .................................. SUCCESS [
>>> 5.147 s]
>>> [INFO] Apache Jena - Base Common Environment .............. FAILURE [
>>> 3.073 s]
>>> [INFO] Apache Jena - Core ................................. SKIPPED
>>> [INFO] Apache Jena - ARQ (SPARQL 1.1 Query Engine) ........ SKIPPED
>>> [INFO] Apache Jena - RDF Connection ....................... SKIPPED
>>> [INFO] Apache Jena - TDB1 (Native Triple Store) ........... SKIPPED
>>> [INFO] Apache Jena - Database Operation Environment ....... SKIPPED
>>> [INFO] Apache Jena - DBOE Base ............................ SKIPPED
>>> [INFO] Apache Jena - DBOE Transactions .................... SKIPPED
>>> [INFO] Apache Jena - DBOE Indexes ......................... SKIPPED
>>> [INFO] Apache Jena - DBOE Index test suite ................ SKIPPED
>>> [INFO] Apache Jena - DBOE Transactional Datastructures .... SKIPPED
>>> [INFO] Apache Jena - TDB2 ................................. SKIPPED
>>> [INFO] Apache Jena - Libraries POM ........................ SKIPPED
>>> [INFO] Apache Jena - Command line tools ................... SKIPPED
>>> [INFO] Apache Jena - SPARQL Text Search ................... SKIPPED
>>> [INFO] Apache Jena - SPARQL Text Search - Elasticsearch ... SKIPPED
>>> [INFO] Apache Jena - SPARQL Spatial Search ................ SKIPPED
>>> [INFO] Apache Jena - Fuseki - A SPARQL 1.1 Server ......... SKIPPED
>>> [INFO] Apache Jena - Fuseki Server Engine ................. SKIPPED
>>> [INFO] Apache Jena - Fuseki Embedded Server ............... SKIPPED
>>> [INFO] Apache Jena - Fuseki WAR File ...................... SKIPPED
>>> [INFO] Apache Jena - Fuseki Server Standalone Jar ......... SKIPPED
>>> [INFO] Apache Jena - Fuseki Basic Server .................. SKIPPED
>>> [INFO] Apache Jena - Fuseki Binary Distribution ........... SKIPPED
>>> [INFO] Apache Jena - Integration Testing .................. SKIPPED
>>> [INFO] Apache Jena - Distribution ......................... SKIPPED
>>> [INFO] Apache Jena - Fuseki1 .............................. SKIPPED
>>> [INFO] Apache Jena - Data Tables for RDF and SPARQL ....... SKIPPED
>>> [INFO] Apache Jena - SDB (SQL based triple store) ......... SKIPPED
>>> [INFO] Apache Jena - Security Permissions ................. SKIPPED
>>> [INFO] Apache Jena - Extras ............................... SKIPPED
>>> [INFO] Apache Jena - Extras - Query Builder ............... SKIPPED
>>> [INFO] Apache Jena - JDBC Parent .......................... SKIPPED
>>> [INFO] Apache Jena - JDBC Core API ........................ SKIPPED
>>> [INFO] Apache Jena - JDBC Remote Endpoint Driver .......... SKIPPED
>>> [INFO] Apache Jena - JDBC In-Memory Driver ................ SKIPPED
>>> [INFO] Apache Jena - JDBC TDB Driver ...................... SKIPPED
>>> [INFO] Apache Jena - JDBC Driver Bundle ................... SKIPPED
>>> [INFO] Apache Jena - Elephas .............................. SKIPPED
>>> [INFO] Apache Jena - Elephas - Common API ................. SKIPPED
>>> [INFO] Apache Jena - Elephas - I/O ........................ SKIPPED
>>> [INFO] Apache Jena - Elephas - Map/Reduce ................. SKIPPED
>>> [INFO] Apache Jena - Elephas - Statistics Demo App ........ SKIPPED
>>> [INFO] Apache Jena - OSGi ................................. SKIPPED
>>> [INFO] Apache Jena - OSGi bundle .......................... SKIPPED
>>> [INFO] Apache Jena - OSGi Karaf features 3.8.0-SNAPSHOT ... SKIPPED
>>> [INFO] ------------------------------------------------------------
>>> ------------
>>> [INFO] BUILD FAILURE
>>> [INFO] ------------------------------------------------------------
>>> ------------
>>> [INFO] Total time: 11.970 s
>>> [INFO] Finished at: 2018-04-03T17:17:15+01:00
>>> [INFO] ------------------------------------------------------------
>>> ------------
>>> [ERROR] Failed to execute goal 
>>> org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar
>>> (attach-javadocs) on project jena-base: Execution attach-javadocs of 
>>> goal
>>> org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar failed.:
>>> NullPointerException -> [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 :jena-base
>>>
>>>
>>>
>>>
>>> On Tue, Apr 3, 2018 at 11:48 AM, Andy Seaborne <an...@apache.org> wrote:
>>>
>>>> Semantic Versioning says nothing about source vs binary compatibility.
>>>>
>>>> The reason for having minor version normally is allow some evolution.
>>>> Jena 3.7.0 is not a patch release.
>>>>
>>>> It is highlighted in "heads up" message to users@jena:
>>>> https://lists.apache.org/thread.html/5b31a3b6794781f6a026586
>>>> 08444043b5535957a6c94f3728efd8304@%3Cusers.jena.apache.org%3E
>>>>
>>>> What else do you want?
>>>>
>>>> We don't offer or test for binary compatibility (which would also 
>>>> include
>>>> the binary compatibility of dependencies because apps may get them via
>>>> depending on Jena). We don't claim drop-in replacement of jars either -
>>>> exactly the opposite in fact. It causes users problems.
>>>>
>>>>>>>> ... but I would like the
>>>>>>>> discussion held and consensus reached before the release goes 
>>>>>>>> ahead.
>>>>
>>>> That's rather vague.
>>>>
>>>> There was discussion on JENA-1389.
>>>> What extra discussion?
>>>>
>>>> ----
>>>>
>>>> It seems me to be rather unhelpful to users to bump the major version
>>>> number every time there is a binary change in any of our modules.  
>>>> We are
>>>> not Common components. Going back to version-per-module is unhelpful 
>>>> (users
>>>> ignored it) as well.
>>>>
>>>>      Andy
>>>>
>>>>
>>>> On 02/04/18 23:22, Claude Warren wrote:
>>>>
>>>>> I am not advocating that we create bridge methods in the  build as is
>>>>> mentioned later in the linke I posted above, just asking about the 
>>>>> proper
>>>>> version numbers.
>>>>>
>>>>> Claude
>>>>>
>>>>> On Mon, Apr 2, 2018 at 11:20 PM, Claude Warren <cl...@xenei.com> 
>>>>> wrote:
>>>>>
>>>>> Sorry, I should have included a link before:
>>>>>>
>>>>>> https://lists.apache.org/list.html?dev@commons.apache.org:
>>>>>> lte=1M:%5Bcollections%5D%20breaking%20changes
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Mon, Apr 2, 2018 at 11:02 AM, Andy Seaborne <an...@apache.org> 
>>>>>> wrote:
>>>>>>
>>>>>> Please see the discussions on the JIRA about source code 
>>>>>> compatibility.
>>>>>>>
>>>>>>> JENA-1389
>>>>>>> https://github.com/apache/jena/pull/362
>>>>>>>
>>>>>>> JENA-1495
>>>>>>> https://github.com/apache/jena/pull/368
>>>>>>>
>>>>>>> Where is that other discussion? A link would be helpful.
>>>>>>>
>>>>>>>       Andy
>>>>>>>
>>>>>>>
>>>>>>> On 02/04/18 10:03, Claude Warren wrote:
>>>>>>>
>>>>>>> Should this not be released as a 4.0 version as I think we operate
>>>>>>>> under
>>>>>>>> semantic versioning and the API is not backwards compatible?
>>>>>>>>
>>>>>>>> There was a similar discussion over in Commons recently where 
>>>>>>>> several
>>>>>>>> of
>>>>>>>> the functions there were changed to return "this" rather than 
>>>>>>>> "void".
>>>>>>>> Like
>>>>>>>> our changes here.  The decision there was to revert those 
>>>>>>>> changes for
>>>>>>>> the
>>>>>>>> current release and place the "this" returning versions in the
>>>>>>>> upcoming
>>>>>>>> version number changing release.
>>>>>>>>
>>>>>>>> as noted in the Commons discussion:
>>>>>>>>
>>>>>>>> The return type is part of the method signature that Java uses 
>>>>>>>> to find
>>>>>>>>
>>>>>>>> resolve references.
>>>>>>>>>
>>>>>>>>> Even changing from void to non-void will cause binary
>>>>>>>>> incompatibility.
>>>>>>>>> (Source-wise, that's fine)
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> I am not certain that I should vote -1 on this issue but I would
>>>>>>>> like the
>>>>>>>> discussion held and consensus reached before the release goes 
>>>>>>>> ahead.
>>>>>>>>
>>>>>>>> Claude
>>>>>>>>
>>>>>>>> On Sun, Apr 1, 2018 at 11:03 PM, ajs6f <aj...@apache.org> wrote:
>>>>>>>>
>>>>>>>> Please vote to approve this release:
>>>>>>>>
>>>>>>>>>
>>>>>>>>>>          [ ] +1 Approve the release
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>> +1
>>>>>>>>>
>>>>>>>>>          [ ]  0 Don't care
>>>>>>>>>
>>>>>>>>>>          [ ] -1 Don't release, because ...
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>> + does everything work on OS X?
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>> Yes.
>>>>>>>>>
>>>>>>>>> + are the GPG signatures fine?
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>> Yes.
>>>>>>>>>
>>>>>>>>> + is there a source archive?
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>> Yes.
>>>>>>>>>
>>>>>>>>> + can the source archive really be built?
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>> Yes.
>>>>>>>>>
>>>>>>>>> ajs6f
>>>>>>>>>
>>>>>>>>> On Mar 29, 2018, at 2:28 PM, Andy Seaborne <an...@apache.org> 
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Hi,
>>>>>>>>>>
>>>>>>>>>> Here is a vote on a release of Jena 3.7.0.
>>>>>>>>>>
>>>>>>>>>> This is the first proposed candidate for a 3.7.0 release.
>>>>>>>>>>
>>>>>>>>>> There are process changes.
>>>>>>>>>>
>>>>>>>>>> Deadline:
>>>>>>>>>>
>>>>>>>>>>          2018-04-01 22:00 UTC
>>>>>>>>>>
>>>>>>>>>> April 1st!
>>>>>>>>>>
>>>>>>>>>> ==== Process Changes
>>>>>>>>>>
>>>>>>>>>> 1/
>>>>>>>>>> MD5 files are being discouraged because MD5 is not secure.  
>>>>>>>>>> Projects
>>>>>>>>>> are
>>>>>>>>>>
>>>>>>>>>> now asked to not publish md5.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> There are no md5 files in the proposed dist/jena area - files on
>>>>>>>>>> Apache
>>>>>>>>>>
>>>>>>>>>> hardware.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> There are sha1 and sha512 checksums.
>>>>>>>>>> * The sha512 is in Linux sha512sum checkable format.
>>>>>>>>>> * The sha1 is whatever maven generated and is the same as will 
>>>>>>>>>> go to
>>>>>>>>>>
>>>>>>>>>> maven central.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> Having the sha1 ties the dist/jena artifacts to maven central (as
>>>>>>>>>> does
>>>>>>>>>>
>>>>>>>>>> the .asc).
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> There are md5 and sha1 in the proposes maven repo staging area 
>>>>>>>>>> for
>>>>>>>>>>
>>>>>>>>>> sending to maven central. That part of maven is hardwired to
>>>>>>>>> md5/sha1
>>>>>>>>> still.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> There's a script to setup the sha512.
>>>>>>>>>>
>>>>>>>>>> 2/
>>>>>>>>>> To establish the proof chain for signed artifacts in
>>>>>>>>>> /dist/project/, I
>>>>>>>>>>
>>>>>>>>>> have been asked to try out the new META files.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> https://checker.apache.org/doc/README.html#ch-meta
>>>>>>>>>>
>>>>>>>>>> There are two files
>>>>>>>>>>
>>>>>>>>>> /dist/jena/META
>>>>>>>>>> /dist/jena/META.asc
>>>>>>>>>>
>>>>>>>>>> META says who signs what, and is itself signed by the PMC chair.
>>>>>>>>>>
>>>>>>>>>> ==== Release changes
>>>>>>>>>>
>>>>>>>>>> 55 JIRA:
>>>>>>>>>> https://s.apache.org/jena-3.7.0-jira
>>>>>>>>>>
>>>>>>>>>> == Significant Changes
>>>>>>>>>>
>>>>>>>>>> ** Java9: Building and running on a Java9 platform is supported
>>>>>>>>>>
>>>>>>>>>> JENA-1461 - Allow ARQ custom functions to be written in 
>>>>>>>>>> JavaScript
>>>>>>>>>>
>>>>>>>>>> JENA-1389 - Return `this` rather than `void` from Dataset (API
>>>>>>>>>> change)
>>>>>>>>>> JENA-1495 - Return Model from PrefixMapping methods (API change)
>>>>>>>>>>
>>>>>>>>>> JENA-1458, JENA-1483 - Transaction Promotion
>>>>>>>>>>
>>>>>>>>>> JENA-1453 - Lucene indexes using a graph field are smaller
>>>>>>>>>>
>>>>>>>>>> JENA-1490 - Working with Blank Nodes with Fuseki
>>>>>>>>>>
>>>>>>>>>> == Upgrades to libraries (runtime dependencies):
>>>>>>>>>>
>>>>>>>>>> No dependency changes.
>>>>>>>>>>
>>>>>>>>>> ==== Release Vote
>>>>>>>>>>
>>>>>>>>>> Everyone, not just committers, is invited to test and vote.
>>>>>>>>>> Please download and test the proposed release.
>>>>>>>>>>
>>>>>>>>>> Proposed dist/ area:
>>>>>>>>>>     https://dist.apache.org/repos/dist/dev/jena/
>>>>>>>>>>
>>>>>>>>>> Keys:
>>>>>>>>>>     https://svn.apache.org/repos/asf/jena/dist/KEYS
>>>>>>>>>>
>>>>>>>>>> Staging repository:
>>>>>>>>>>     https://repository.apache.org/content/repositories/orgapache
>>>>>>>>>> jena-1022/
>>>>>>>>>>
>>>>>>>>>> Git commit (browser URL):
>>>>>>>>>> https://git1-us-west.apache.org/repos/asf?p=jena.git;a=commi
>>>>>>>>>> t;h=d4e7063e
>>>>>>>>>>
>>>>>>>>>> Git Commit Hash:
>>>>>>>>>>     d4e7063e7a6db8ce77699bd0388e1a1bd6816626
>>>>>>>>>>
>>>>>>>>>> Git Commit Tag:
>>>>>>>>>>        jena-3.7.0-rc1
>>>>>>>>>>
>>>>>>>>>> Please vote to approve this release:
>>>>>>>>>>
>>>>>>>>>>          [ ] +1 Approve the release
>>>>>>>>>>          [ ]  0 Don't care
>>>>>>>>>>          [ ] -1 Don't release, because ...
>>>>>>>>>>
>>>>>>>>>> This vote will be open until at least
>>>>>>>>>>
>>>>>>>>>>          2018-04-01 22:00 UTC
>>>>>>>>>>
>>>>>>>>>> If you expect to check the release but the time 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?
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>
>>>>>> -- 
>>>>>> I like: Like Like - The likeliest place on the web
>>>>>> <http://like-like.xenei.com>
>>>>>> LinkedIn: http://www.linkedin.com/in/claudewarren
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>
>>>
>>> -- 
>>> I like: Like Like - The likeliest place on the web
>>> <http://like-like.xenei.com>
>>> LinkedIn: http://www.linkedin.com/in/claudewarren
>>>
>>
>>
>>

Re: [] Apache Jena 3.7.0 RC1

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

1/ This is 3.8.0-SNAPSHOT - not the release candidate.

2/ Jenkins has been building 3.8.0-SNAPSHOT including javadoc.

3/ It says it is in the javadoc plugin:

"""
org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar failed.:
NullPointerException -> [Help 1]
"""

so we have very little control there.

(-Pdev does not produce javadoc.)

Best I can suggest is completely clear out the M2 repo of 3.8.0-SNAPSHOT 
items and retry.

I will try on my machine when I can. (I am conducting timed runs for the 
users@ report ATM.)

     Andy

On 03/04/18 17:30, Claude Warren wrote:
> Sorry, should have added:
> 
> openjdk version "1.8.0_162"
> OpenJDK Runtime Environment (build 1.8.0_162-8u162-b12-0ubuntu0.16.04.2-b12)
> OpenJDK 64-Bit Server VM (build 25.162-b12, mixed mode)
> 
> Linux claude-XPS-15-9560 4.13.0-37-generic #42~16.04.1-Ubuntu SMP Wed Mar 7
> 16:03:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
> 
> 
> 
> 
> On Tue, Apr 3, 2018 at 5:20 PM, Claude Warren <cl...@xenei.com> wrote:
> 
>> Compile on Ubuntu with clone from git fails.
>>
>> mvn clean install -Pdev
>>
>> success
>>
>> mvn clean install
>>
>> fails with:
>>
>> [INFO] --- maven-javadoc-plugin:3.0.0:jar (attach-javadocs) @ jena-base ---
>> [INFO] The goal 'org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:javadoc'
>> has not been previously called for the module: 'org.apache.jena:jena-shaded-guava:jar:3.8.0-SNAPSHOT'.
>> Trying to invoke it...
>> [WARNING] Creating fake javadoc directory to prevent repeated invocations:
>> /home/claude/git/jena/jena-shaded-guava/target/apidocs
>> [INFO] ------------------------------------------------------------
>> ------------
>> [INFO] Reactor Summary:
>> [INFO]
>> [INFO] Apache Jena 3.8.0-SNAPSHOT ......................... SUCCESS [
>> 1.502 s]
>> [INFO] Apache Jena - Shadowed external libraries .......... SUCCESS [
>> 1.545 s]
>> [INFO] Apache Jena - IRI .................................. SUCCESS [
>> 5.147 s]
>> [INFO] Apache Jena - Base Common Environment .............. FAILURE [
>> 3.073 s]
>> [INFO] Apache Jena - Core ................................. SKIPPED
>> [INFO] Apache Jena - ARQ (SPARQL 1.1 Query Engine) ........ SKIPPED
>> [INFO] Apache Jena - RDF Connection ....................... SKIPPED
>> [INFO] Apache Jena - TDB1 (Native Triple Store) ........... SKIPPED
>> [INFO] Apache Jena - Database Operation Environment ....... SKIPPED
>> [INFO] Apache Jena - DBOE Base ............................ SKIPPED
>> [INFO] Apache Jena - DBOE Transactions .................... SKIPPED
>> [INFO] Apache Jena - DBOE Indexes ......................... SKIPPED
>> [INFO] Apache Jena - DBOE Index test suite ................ SKIPPED
>> [INFO] Apache Jena - DBOE Transactional Datastructures .... SKIPPED
>> [INFO] Apache Jena - TDB2 ................................. SKIPPED
>> [INFO] Apache Jena - Libraries POM ........................ SKIPPED
>> [INFO] Apache Jena - Command line tools ................... SKIPPED
>> [INFO] Apache Jena - SPARQL Text Search ................... SKIPPED
>> [INFO] Apache Jena - SPARQL Text Search - Elasticsearch ... SKIPPED
>> [INFO] Apache Jena - SPARQL Spatial Search ................ SKIPPED
>> [INFO] Apache Jena - Fuseki - A SPARQL 1.1 Server ......... SKIPPED
>> [INFO] Apache Jena - Fuseki Server Engine ................. SKIPPED
>> [INFO] Apache Jena - Fuseki Embedded Server ............... SKIPPED
>> [INFO] Apache Jena - Fuseki WAR File ...................... SKIPPED
>> [INFO] Apache Jena - Fuseki Server Standalone Jar ......... SKIPPED
>> [INFO] Apache Jena - Fuseki Basic Server .................. SKIPPED
>> [INFO] Apache Jena - Fuseki Binary Distribution ........... SKIPPED
>> [INFO] Apache Jena - Integration Testing .................. SKIPPED
>> [INFO] Apache Jena - Distribution ......................... SKIPPED
>> [INFO] Apache Jena - Fuseki1 .............................. SKIPPED
>> [INFO] Apache Jena - Data Tables for RDF and SPARQL ....... SKIPPED
>> [INFO] Apache Jena - SDB (SQL based triple store) ......... SKIPPED
>> [INFO] Apache Jena - Security Permissions ................. SKIPPED
>> [INFO] Apache Jena - Extras ............................... SKIPPED
>> [INFO] Apache Jena - Extras - Query Builder ............... SKIPPED
>> [INFO] Apache Jena - JDBC Parent .......................... SKIPPED
>> [INFO] Apache Jena - JDBC Core API ........................ SKIPPED
>> [INFO] Apache Jena - JDBC Remote Endpoint Driver .......... SKIPPED
>> [INFO] Apache Jena - JDBC In-Memory Driver ................ SKIPPED
>> [INFO] Apache Jena - JDBC TDB Driver ...................... SKIPPED
>> [INFO] Apache Jena - JDBC Driver Bundle ................... SKIPPED
>> [INFO] Apache Jena - Elephas .............................. SKIPPED
>> [INFO] Apache Jena - Elephas - Common API ................. SKIPPED
>> [INFO] Apache Jena - Elephas - I/O ........................ SKIPPED
>> [INFO] Apache Jena - Elephas - Map/Reduce ................. SKIPPED
>> [INFO] Apache Jena - Elephas - Statistics Demo App ........ SKIPPED
>> [INFO] Apache Jena - OSGi ................................. SKIPPED
>> [INFO] Apache Jena - OSGi bundle .......................... SKIPPED
>> [INFO] Apache Jena - OSGi Karaf features 3.8.0-SNAPSHOT ... SKIPPED
>> [INFO] ------------------------------------------------------------
>> ------------
>> [INFO] BUILD FAILURE
>> [INFO] ------------------------------------------------------------
>> ------------
>> [INFO] Total time: 11.970 s
>> [INFO] Finished at: 2018-04-03T17:17:15+01:00
>> [INFO] ------------------------------------------------------------
>> ------------
>> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar
>> (attach-javadocs) on project jena-base: Execution attach-javadocs of goal
>> org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar failed.:
>> NullPointerException -> [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 :jena-base
>>
>>
>>
>>
>> On Tue, Apr 3, 2018 at 11:48 AM, Andy Seaborne <an...@apache.org> wrote:
>>
>>> Semantic Versioning says nothing about source vs binary compatibility.
>>>
>>> The reason for having minor version normally is allow some evolution.
>>> Jena 3.7.0 is not a patch release.
>>>
>>> It is highlighted in "heads up" message to users@jena:
>>> https://lists.apache.org/thread.html/5b31a3b6794781f6a026586
>>> 08444043b5535957a6c94f3728efd8304@%3Cusers.jena.apache.org%3E
>>>
>>> What else do you want?
>>>
>>> We don't offer or test for binary compatibility (which would also include
>>> the binary compatibility of dependencies because apps may get them via
>>> depending on Jena). We don't claim drop-in replacement of jars either -
>>> exactly the opposite in fact. It causes users problems.
>>>
>>>>>>> ... but I would like the
>>>>>>> discussion held and consensus reached before the release goes ahead.
>>>
>>> That's rather vague.
>>>
>>> There was discussion on JENA-1389.
>>> What extra discussion?
>>>
>>> ----
>>>
>>> It seems me to be rather unhelpful to users to bump the major version
>>> number every time there is a binary change in any of our modules.  We are
>>> not Common components. Going back to version-per-module is unhelpful (users
>>> ignored it) as well.
>>>
>>>      Andy
>>>
>>>
>>> On 02/04/18 23:22, Claude Warren wrote:
>>>
>>>> I am not advocating that we create bridge methods in the  build as is
>>>> mentioned later in the linke I posted above, just asking about the proper
>>>> version numbers.
>>>>
>>>> Claude
>>>>
>>>> On Mon, Apr 2, 2018 at 11:20 PM, Claude Warren <cl...@xenei.com> wrote:
>>>>
>>>> Sorry, I should have included a link before:
>>>>>
>>>>> https://lists.apache.org/list.html?dev@commons.apache.org:
>>>>> lte=1M:%5Bcollections%5D%20breaking%20changes
>>>>>
>>>>>
>>>>>
>>>>> On Mon, Apr 2, 2018 at 11:02 AM, Andy Seaborne <an...@apache.org> wrote:
>>>>>
>>>>> Please see the discussions on the JIRA about source code compatibility.
>>>>>>
>>>>>> JENA-1389
>>>>>> https://github.com/apache/jena/pull/362
>>>>>>
>>>>>> JENA-1495
>>>>>> https://github.com/apache/jena/pull/368
>>>>>>
>>>>>> Where is that other discussion? A link would be helpful.
>>>>>>
>>>>>>       Andy
>>>>>>
>>>>>>
>>>>>> On 02/04/18 10:03, Claude Warren wrote:
>>>>>>
>>>>>> Should this not be released as a 4.0 version as I think we operate
>>>>>>> under
>>>>>>> semantic versioning and the API is not backwards compatible?
>>>>>>>
>>>>>>> There was a similar discussion over in Commons recently where several
>>>>>>> of
>>>>>>> the functions there were changed to return "this" rather than "void".
>>>>>>> Like
>>>>>>> our changes here.  The decision there was to revert those changes for
>>>>>>> the
>>>>>>> current release and place the "this" returning versions in the
>>>>>>> upcoming
>>>>>>> version number changing release.
>>>>>>>
>>>>>>> as noted in the Commons discussion:
>>>>>>>
>>>>>>> The return type is part of the method signature that Java uses to find
>>>>>>>
>>>>>>> resolve references.
>>>>>>>>
>>>>>>>> Even changing from void to non-void will cause binary
>>>>>>>> incompatibility.
>>>>>>>> (Source-wise, that's fine)
>>>>>>>>
>>>>>>>>
>>>>>>>> I am not certain that I should vote -1 on this issue but I would
>>>>>>> like the
>>>>>>> discussion held and consensus reached before the release goes ahead.
>>>>>>>
>>>>>>> Claude
>>>>>>>
>>>>>>> On Sun, Apr 1, 2018 at 11:03 PM, ajs6f <aj...@apache.org> wrote:
>>>>>>>
>>>>>>> Please vote to approve this release:
>>>>>>>
>>>>>>>>
>>>>>>>>>          [ ] +1 Approve the release
>>>>>>>>>
>>>>>>>>>
>>>>>>>> +1
>>>>>>>>
>>>>>>>>          [ ]  0 Don't care
>>>>>>>>
>>>>>>>>>          [ ] -1 Don't release, because ...
>>>>>>>>>
>>>>>>>>>
>>>>>>>> + does everything work on OS X?
>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>> Yes.
>>>>>>>>
>>>>>>>> + are the GPG signatures fine?
>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>> Yes.
>>>>>>>>
>>>>>>>> + is there a source archive?
>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>> Yes.
>>>>>>>>
>>>>>>>> + can the source archive really be built?
>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>> Yes.
>>>>>>>>
>>>>>>>> ajs6f
>>>>>>>>
>>>>>>>> On Mar 29, 2018, at 2:28 PM, Andy Seaborne <an...@apache.org> wrote:
>>>>>>>>
>>>>>>>>>
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> Here is a vote on a release of Jena 3.7.0.
>>>>>>>>>
>>>>>>>>> This is the first proposed candidate for a 3.7.0 release.
>>>>>>>>>
>>>>>>>>> There are process changes.
>>>>>>>>>
>>>>>>>>> Deadline:
>>>>>>>>>
>>>>>>>>>          2018-04-01 22:00 UTC
>>>>>>>>>
>>>>>>>>> April 1st!
>>>>>>>>>
>>>>>>>>> ==== Process Changes
>>>>>>>>>
>>>>>>>>> 1/
>>>>>>>>> MD5 files are being discouraged because MD5 is not secure.  Projects
>>>>>>>>> are
>>>>>>>>>
>>>>>>>>> now asked to not publish md5.
>>>>>>>>
>>>>>>>>
>>>>>>>>> There are no md5 files in the proposed dist/jena area - files on
>>>>>>>>> Apache
>>>>>>>>>
>>>>>>>>> hardware.
>>>>>>>>
>>>>>>>>
>>>>>>>>> There are sha1 and sha512 checksums.
>>>>>>>>> * The sha512 is in Linux sha512sum checkable format.
>>>>>>>>> * The sha1 is whatever maven generated and is the same as will go to
>>>>>>>>>
>>>>>>>>> maven central.
>>>>>>>>
>>>>>>>>
>>>>>>>>> Having the sha1 ties the dist/jena artifacts to maven central (as
>>>>>>>>> does
>>>>>>>>>
>>>>>>>>> the .asc).
>>>>>>>>
>>>>>>>>
>>>>>>>>> There are md5 and sha1 in the proposes maven repo staging area for
>>>>>>>>>
>>>>>>>>> sending to maven central. That part of maven is hardwired to
>>>>>>>> md5/sha1
>>>>>>>> still.
>>>>>>>>
>>>>>>>>
>>>>>>>>> There's a script to setup the sha512.
>>>>>>>>>
>>>>>>>>> 2/
>>>>>>>>> To establish the proof chain for signed artifacts in
>>>>>>>>> /dist/project/, I
>>>>>>>>>
>>>>>>>>> have been asked to try out the new META files.
>>>>>>>>
>>>>>>>>
>>>>>>>>> https://checker.apache.org/doc/README.html#ch-meta
>>>>>>>>>
>>>>>>>>> There are two files
>>>>>>>>>
>>>>>>>>> /dist/jena/META
>>>>>>>>> /dist/jena/META.asc
>>>>>>>>>
>>>>>>>>> META says who signs what, and is itself signed by the PMC chair.
>>>>>>>>>
>>>>>>>>> ==== Release changes
>>>>>>>>>
>>>>>>>>> 55 JIRA:
>>>>>>>>> https://s.apache.org/jena-3.7.0-jira
>>>>>>>>>
>>>>>>>>> == Significant Changes
>>>>>>>>>
>>>>>>>>> ** Java9: Building and running on a Java9 platform is supported
>>>>>>>>>
>>>>>>>>> JENA-1461 - Allow ARQ custom functions to be written in JavaScript
>>>>>>>>>
>>>>>>>>> JENA-1389 - Return `this` rather than `void` from Dataset (API
>>>>>>>>> change)
>>>>>>>>> JENA-1495 - Return Model from PrefixMapping methods (API change)
>>>>>>>>>
>>>>>>>>> JENA-1458, JENA-1483 - Transaction Promotion
>>>>>>>>>
>>>>>>>>> JENA-1453 - Lucene indexes using a graph field are smaller
>>>>>>>>>
>>>>>>>>> JENA-1490 - Working with Blank Nodes with Fuseki
>>>>>>>>>
>>>>>>>>> == Upgrades to libraries (runtime dependencies):
>>>>>>>>>
>>>>>>>>> No dependency changes.
>>>>>>>>>
>>>>>>>>> ==== Release Vote
>>>>>>>>>
>>>>>>>>> Everyone, not just committers, is invited to test and vote.
>>>>>>>>> Please download and test the proposed release.
>>>>>>>>>
>>>>>>>>> Proposed dist/ area:
>>>>>>>>>     https://dist.apache.org/repos/dist/dev/jena/
>>>>>>>>>
>>>>>>>>> Keys:
>>>>>>>>>     https://svn.apache.org/repos/asf/jena/dist/KEYS
>>>>>>>>>
>>>>>>>>> Staging repository:
>>>>>>>>>     https://repository.apache.org/content/repositories/orgapache
>>>>>>>>> jena-1022/
>>>>>>>>>
>>>>>>>>> Git commit (browser URL):
>>>>>>>>> https://git1-us-west.apache.org/repos/asf?p=jena.git;a=commi
>>>>>>>>> t;h=d4e7063e
>>>>>>>>>
>>>>>>>>> Git Commit Hash:
>>>>>>>>>     d4e7063e7a6db8ce77699bd0388e1a1bd6816626
>>>>>>>>>
>>>>>>>>> Git Commit Tag:
>>>>>>>>>        jena-3.7.0-rc1
>>>>>>>>>
>>>>>>>>> Please vote to approve this release:
>>>>>>>>>
>>>>>>>>>          [ ] +1 Approve the release
>>>>>>>>>          [ ]  0 Don't care
>>>>>>>>>          [ ] -1 Don't release, because ...
>>>>>>>>>
>>>>>>>>> This vote will be open until at least
>>>>>>>>>
>>>>>>>>>          2018-04-01 22:00 UTC
>>>>>>>>>
>>>>>>>>> If you expect to check the release but the time 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?
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>
>>>>> --
>>>>> I like: Like Like - The likeliest place on the web
>>>>> <http://like-like.xenei.com>
>>>>> LinkedIn: http://www.linkedin.com/in/claudewarren
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>
>>
>> --
>> I like: Like Like - The likeliest place on the web
>> <http://like-like.xenei.com>
>> LinkedIn: http://www.linkedin.com/in/claudewarren
>>
> 
> 
>

Re: [] Apache Jena 3.7.0 RC1

Posted by Claude Warren <cl...@xenei.com>.

Sorry, should have added:

openjdk version "1.8.0_162"
OpenJDK Runtime Environment (build 1.8.0_162-8u162-b12-0ubuntu0.16.04.2-b12)
OpenJDK 64-Bit Server VM (build 25.162-b12, mixed mode)

Linux claude-XPS-15-9560 4.13.0-37-generic #42~16.04.1-Ubuntu SMP Wed Mar 7
16:03:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux




On Tue, Apr 3, 2018 at 5:20 PM, Claude Warren <cl...@xenei.com> wrote:

> Compile on Ubuntu with clone from git fails.
>
> mvn clean install -Pdev
>
> success
>
> mvn clean install
>
> fails with:
>
> [INFO] --- maven-javadoc-plugin:3.0.0:jar (attach-javadocs) @ jena-base ---
> [INFO] The goal 'org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:javadoc'
> has not been previously called for the module: 'org.apache.jena:jena-shaded-guava:jar:3.8.0-SNAPSHOT'.
> Trying to invoke it...
> [WARNING] Creating fake javadoc directory to prevent repeated invocations:
> /home/claude/git/jena/jena-shaded-guava/target/apidocs
> [INFO] ------------------------------------------------------------
> ------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache Jena 3.8.0-SNAPSHOT ......................... SUCCESS [
> 1.502 s]
> [INFO] Apache Jena - Shadowed external libraries .......... SUCCESS [
> 1.545 s]
> [INFO] Apache Jena - IRI .................................. SUCCESS [
> 5.147 s]
> [INFO] Apache Jena - Base Common Environment .............. FAILURE [
> 3.073 s]
> [INFO] Apache Jena - Core ................................. SKIPPED
> [INFO] Apache Jena - ARQ (SPARQL 1.1 Query Engine) ........ SKIPPED
> [INFO] Apache Jena - RDF Connection ....................... SKIPPED
> [INFO] Apache Jena - TDB1 (Native Triple Store) ........... SKIPPED
> [INFO] Apache Jena - Database Operation Environment ....... SKIPPED
> [INFO] Apache Jena - DBOE Base ............................ SKIPPED
> [INFO] Apache Jena - DBOE Transactions .................... SKIPPED
> [INFO] Apache Jena - DBOE Indexes ......................... SKIPPED
> [INFO] Apache Jena - DBOE Index test suite ................ SKIPPED
> [INFO] Apache Jena - DBOE Transactional Datastructures .... SKIPPED
> [INFO] Apache Jena - TDB2 ................................. SKIPPED
> [INFO] Apache Jena - Libraries POM ........................ SKIPPED
> [INFO] Apache Jena - Command line tools ................... SKIPPED
> [INFO] Apache Jena - SPARQL Text Search ................... SKIPPED
> [INFO] Apache Jena - SPARQL Text Search - Elasticsearch ... SKIPPED
> [INFO] Apache Jena - SPARQL Spatial Search ................ SKIPPED
> [INFO] Apache Jena - Fuseki - A SPARQL 1.1 Server ......... SKIPPED
> [INFO] Apache Jena - Fuseki Server Engine ................. SKIPPED
> [INFO] Apache Jena - Fuseki Embedded Server ............... SKIPPED
> [INFO] Apache Jena - Fuseki WAR File ...................... SKIPPED
> [INFO] Apache Jena - Fuseki Server Standalone Jar ......... SKIPPED
> [INFO] Apache Jena - Fuseki Basic Server .................. SKIPPED
> [INFO] Apache Jena - Fuseki Binary Distribution ........... SKIPPED
> [INFO] Apache Jena - Integration Testing .................. SKIPPED
> [INFO] Apache Jena - Distribution ......................... SKIPPED
> [INFO] Apache Jena - Fuseki1 .............................. SKIPPED
> [INFO] Apache Jena - Data Tables for RDF and SPARQL ....... SKIPPED
> [INFO] Apache Jena - SDB (SQL based triple store) ......... SKIPPED
> [INFO] Apache Jena - Security Permissions ................. SKIPPED
> [INFO] Apache Jena - Extras ............................... SKIPPED
> [INFO] Apache Jena - Extras - Query Builder ............... SKIPPED
> [INFO] Apache Jena - JDBC Parent .......................... SKIPPED
> [INFO] Apache Jena - JDBC Core API ........................ SKIPPED
> [INFO] Apache Jena - JDBC Remote Endpoint Driver .......... SKIPPED
> [INFO] Apache Jena - JDBC In-Memory Driver ................ SKIPPED
> [INFO] Apache Jena - JDBC TDB Driver ...................... SKIPPED
> [INFO] Apache Jena - JDBC Driver Bundle ................... SKIPPED
> [INFO] Apache Jena - Elephas .............................. SKIPPED
> [INFO] Apache Jena - Elephas - Common API ................. SKIPPED
> [INFO] Apache Jena - Elephas - I/O ........................ SKIPPED
> [INFO] Apache Jena - Elephas - Map/Reduce ................. SKIPPED
> [INFO] Apache Jena - Elephas - Statistics Demo App ........ SKIPPED
> [INFO] Apache Jena - OSGi ................................. SKIPPED
> [INFO] Apache Jena - OSGi bundle .......................... SKIPPED
> [INFO] Apache Jena - OSGi Karaf features 3.8.0-SNAPSHOT ... SKIPPED
> [INFO] ------------------------------------------------------------
> ------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------
> ------------
> [INFO] Total time: 11.970 s
> [INFO] Finished at: 2018-04-03T17:17:15+01:00
> [INFO] ------------------------------------------------------------
> ------------
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar
> (attach-javadocs) on project jena-base: Execution attach-javadocs of goal
> org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar failed.:
> NullPointerException -> [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 :jena-base
>
>
>
>
> On Tue, Apr 3, 2018 at 11:48 AM, Andy Seaborne <an...@apache.org> wrote:
>
>> Semantic Versioning says nothing about source vs binary compatibility.
>>
>> The reason for having minor version normally is allow some evolution.
>> Jena 3.7.0 is not a patch release.
>>
>> It is highlighted in "heads up" message to users@jena:
>> https://lists.apache.org/thread.html/5b31a3b6794781f6a026586
>> 08444043b5535957a6c94f3728efd8304@%3Cusers.jena.apache.org%3E
>>
>> What else do you want?
>>
>> We don't offer or test for binary compatibility (which would also include
>> the binary compatibility of dependencies because apps may get them via
>> depending on Jena). We don't claim drop-in replacement of jars either -
>> exactly the opposite in fact. It causes users problems.
>>
>> >>>> ... but I would like the
>> >>>> discussion held and consensus reached before the release goes ahead.
>>
>> That's rather vague.
>>
>> There was discussion on JENA-1389.
>> What extra discussion?
>>
>> ----
>>
>> It seems me to be rather unhelpful to users to bump the major version
>> number every time there is a binary change in any of our modules.  We are
>> not Common components. Going back to version-per-module is unhelpful (users
>> ignored it) as well.
>>
>>     Andy
>>
>>
>> On 02/04/18 23:22, Claude Warren wrote:
>>
>>> I am not advocating that we create bridge methods in the  build as is
>>> mentioned later in the linke I posted above, just asking about the proper
>>> version numbers.
>>>
>>> Claude
>>>
>>> On Mon, Apr 2, 2018 at 11:20 PM, Claude Warren <cl...@xenei.com> wrote:
>>>
>>> Sorry, I should have included a link before:
>>>>
>>>> https://lists.apache.org/list.html?dev@commons.apache.org:
>>>> lte=1M:%5Bcollections%5D%20breaking%20changes
>>>>
>>>>
>>>>
>>>> On Mon, Apr 2, 2018 at 11:02 AM, Andy Seaborne <an...@apache.org> wrote:
>>>>
>>>> Please see the discussions on the JIRA about source code compatibility.
>>>>>
>>>>> JENA-1389
>>>>> https://github.com/apache/jena/pull/362
>>>>>
>>>>> JENA-1495
>>>>> https://github.com/apache/jena/pull/368
>>>>>
>>>>> Where is that other discussion? A link would be helpful.
>>>>>
>>>>>      Andy
>>>>>
>>>>>
>>>>> On 02/04/18 10:03, Claude Warren wrote:
>>>>>
>>>>> Should this not be released as a 4.0 version as I think we operate
>>>>>> under
>>>>>> semantic versioning and the API is not backwards compatible?
>>>>>>
>>>>>> There was a similar discussion over in Commons recently where several
>>>>>> of
>>>>>> the functions there were changed to return "this" rather than "void".
>>>>>> Like
>>>>>> our changes here.  The decision there was to revert those changes for
>>>>>> the
>>>>>> current release and place the "this" returning versions in the
>>>>>> upcoming
>>>>>> version number changing release.
>>>>>>
>>>>>> as noted in the Commons discussion:
>>>>>>
>>>>>> The return type is part of the method signature that Java uses to find
>>>>>>
>>>>>> resolve references.
>>>>>>>
>>>>>>> Even changing from void to non-void will cause binary
>>>>>>> incompatibility.
>>>>>>> (Source-wise, that's fine)
>>>>>>>
>>>>>>>
>>>>>>> I am not certain that I should vote -1 on this issue but I would
>>>>>> like the
>>>>>> discussion held and consensus reached before the release goes ahead.
>>>>>>
>>>>>> Claude
>>>>>>
>>>>>> On Sun, Apr 1, 2018 at 11:03 PM, ajs6f <aj...@apache.org> wrote:
>>>>>>
>>>>>> Please vote to approve this release:
>>>>>>
>>>>>>>
>>>>>>>>         [ ] +1 Approve the release
>>>>>>>>
>>>>>>>>
>>>>>>> +1
>>>>>>>
>>>>>>>         [ ]  0 Don't care
>>>>>>>
>>>>>>>>         [ ] -1 Don't release, because ...
>>>>>>>>
>>>>>>>>
>>>>>>> + does everything work on OS X?
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>> Yes.
>>>>>>>
>>>>>>> + are the GPG signatures fine?
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>> Yes.
>>>>>>>
>>>>>>> + is there a source archive?
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>> Yes.
>>>>>>>
>>>>>>> + can the source archive really be built?
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>> Yes.
>>>>>>>
>>>>>>> ajs6f
>>>>>>>
>>>>>>> On Mar 29, 2018, at 2:28 PM, Andy Seaborne <an...@apache.org> wrote:
>>>>>>>
>>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> Here is a vote on a release of Jena 3.7.0.
>>>>>>>>
>>>>>>>> This is the first proposed candidate for a 3.7.0 release.
>>>>>>>>
>>>>>>>> There are process changes.
>>>>>>>>
>>>>>>>> Deadline:
>>>>>>>>
>>>>>>>>         2018-04-01 22:00 UTC
>>>>>>>>
>>>>>>>> April 1st!
>>>>>>>>
>>>>>>>> ==== Process Changes
>>>>>>>>
>>>>>>>> 1/
>>>>>>>> MD5 files are being discouraged because MD5 is not secure.  Projects
>>>>>>>> are
>>>>>>>>
>>>>>>>> now asked to not publish md5.
>>>>>>>
>>>>>>>
>>>>>>>> There are no md5 files in the proposed dist/jena area - files on
>>>>>>>> Apache
>>>>>>>>
>>>>>>>> hardware.
>>>>>>>
>>>>>>>
>>>>>>>> There are sha1 and sha512 checksums.
>>>>>>>> * The sha512 is in Linux sha512sum checkable format.
>>>>>>>> * The sha1 is whatever maven generated and is the same as will go to
>>>>>>>>
>>>>>>>> maven central.
>>>>>>>
>>>>>>>
>>>>>>>> Having the sha1 ties the dist/jena artifacts to maven central (as
>>>>>>>> does
>>>>>>>>
>>>>>>>> the .asc).
>>>>>>>
>>>>>>>
>>>>>>>> There are md5 and sha1 in the proposes maven repo staging area for
>>>>>>>>
>>>>>>>> sending to maven central. That part of maven is hardwired to
>>>>>>> md5/sha1
>>>>>>> still.
>>>>>>>
>>>>>>>
>>>>>>>> There's a script to setup the sha512.
>>>>>>>>
>>>>>>>> 2/
>>>>>>>> To establish the proof chain for signed artifacts in
>>>>>>>> /dist/project/, I
>>>>>>>>
>>>>>>>> have been asked to try out the new META files.
>>>>>>>
>>>>>>>
>>>>>>>> https://checker.apache.org/doc/README.html#ch-meta
>>>>>>>>
>>>>>>>> There are two files
>>>>>>>>
>>>>>>>> /dist/jena/META
>>>>>>>> /dist/jena/META.asc
>>>>>>>>
>>>>>>>> META says who signs what, and is itself signed by the PMC chair.
>>>>>>>>
>>>>>>>> ==== Release changes
>>>>>>>>
>>>>>>>> 55 JIRA:
>>>>>>>> https://s.apache.org/jena-3.7.0-jira
>>>>>>>>
>>>>>>>> == Significant Changes
>>>>>>>>
>>>>>>>> ** Java9: Building and running on a Java9 platform is supported
>>>>>>>>
>>>>>>>> JENA-1461 - Allow ARQ custom functions to be written in JavaScript
>>>>>>>>
>>>>>>>> JENA-1389 - Return `this` rather than `void` from Dataset (API
>>>>>>>> change)
>>>>>>>> JENA-1495 - Return Model from PrefixMapping methods (API change)
>>>>>>>>
>>>>>>>> JENA-1458, JENA-1483 - Transaction Promotion
>>>>>>>>
>>>>>>>> JENA-1453 - Lucene indexes using a graph field are smaller
>>>>>>>>
>>>>>>>> JENA-1490 - Working with Blank Nodes with Fuseki
>>>>>>>>
>>>>>>>> == Upgrades to libraries (runtime dependencies):
>>>>>>>>
>>>>>>>> No dependency changes.
>>>>>>>>
>>>>>>>> ==== Release Vote
>>>>>>>>
>>>>>>>> Everyone, not just committers, is invited to test and vote.
>>>>>>>> Please download and test the proposed release.
>>>>>>>>
>>>>>>>> Proposed dist/ area:
>>>>>>>>    https://dist.apache.org/repos/dist/dev/jena/
>>>>>>>>
>>>>>>>> Keys:
>>>>>>>>    https://svn.apache.org/repos/asf/jena/dist/KEYS
>>>>>>>>
>>>>>>>> Staging repository:
>>>>>>>>    https://repository.apache.org/content/repositories/orgapache
>>>>>>>> jena-1022/
>>>>>>>>
>>>>>>>> Git commit (browser URL):
>>>>>>>> https://git1-us-west.apache.org/repos/asf?p=jena.git;a=commi
>>>>>>>> t;h=d4e7063e
>>>>>>>>
>>>>>>>> Git Commit Hash:
>>>>>>>>    d4e7063e7a6db8ce77699bd0388e1a1bd6816626
>>>>>>>>
>>>>>>>> Git Commit Tag:
>>>>>>>>       jena-3.7.0-rc1
>>>>>>>>
>>>>>>>> Please vote to approve this release:
>>>>>>>>
>>>>>>>>         [ ] +1 Approve the release
>>>>>>>>         [ ]  0 Don't care
>>>>>>>>         [ ] -1 Don't release, because ...
>>>>>>>>
>>>>>>>> This vote will be open until at least
>>>>>>>>
>>>>>>>>         2018-04-01 22:00 UTC
>>>>>>>>
>>>>>>>> If you expect to check the release but the time 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?
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>
>>>> --
>>>> I like: Like Like - The likeliest place on the web
>>>> <http://like-like.xenei.com>
>>>> LinkedIn: http://www.linkedin.com/in/claudewarren
>>>>
>>>>
>>>
>>>
>>>
>
>
> --
> I like: Like Like - The likeliest place on the web
> <http://like-like.xenei.com>
> LinkedIn: http://www.linkedin.com/in/claudewarren
>



-- 
I like: Like Like - The likeliest place on the web
<http://like-like.xenei.com>
LinkedIn: http://www.linkedin.com/in/claudewarren

Re: [] Apache Jena 3.7.0 RC1

Posted by Claude Warren <cl...@xenei.com>.

Compile on Ubuntu with clone from git fails.

mvn clean install -Pdev

success

mvn clean install

fails with:

[INFO] --- maven-javadoc-plugin:3.0.0:jar (attach-javadocs) @ jena-base ---
[INFO] The goal
'org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:javadoc' has not been
previously called for the module:
'org.apache.jena:jena-shaded-guava:jar:3.8.0-SNAPSHOT'. Trying to invoke
it...
[WARNING] Creating fake javadoc directory to prevent repeated invocations:
/home/claude/git/jena/jena-shaded-guava/target/apidocs
[INFO]
------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Jena 3.8.0-SNAPSHOT ......................... SUCCESS [
1.502 s]
[INFO] Apache Jena - Shadowed external libraries .......... SUCCESS [
1.545 s]
[INFO] Apache Jena - IRI .................................. SUCCESS [
5.147 s]
[INFO] Apache Jena - Base Common Environment .............. FAILURE [
3.073 s]
[INFO] Apache Jena - Core ................................. SKIPPED
[INFO] Apache Jena - ARQ (SPARQL 1.1 Query Engine) ........ SKIPPED
[INFO] Apache Jena - RDF Connection ....................... SKIPPED
[INFO] Apache Jena - TDB1 (Native Triple Store) ........... SKIPPED
[INFO] Apache Jena - Database Operation Environment ....... SKIPPED
[INFO] Apache Jena - DBOE Base ............................ SKIPPED
[INFO] Apache Jena - DBOE Transactions .................... SKIPPED
[INFO] Apache Jena - DBOE Indexes ......................... SKIPPED
[INFO] Apache Jena - DBOE Index test suite ................ SKIPPED
[INFO] Apache Jena - DBOE Transactional Datastructures .... SKIPPED
[INFO] Apache Jena - TDB2 ................................. SKIPPED
[INFO] Apache Jena - Libraries POM ........................ SKIPPED
[INFO] Apache Jena - Command line tools ................... SKIPPED
[INFO] Apache Jena - SPARQL Text Search ................... SKIPPED
[INFO] Apache Jena - SPARQL Text Search - Elasticsearch ... SKIPPED
[INFO] Apache Jena - SPARQL Spatial Search ................ SKIPPED
[INFO] Apache Jena - Fuseki - A SPARQL 1.1 Server ......... SKIPPED
[INFO] Apache Jena - Fuseki Server Engine ................. SKIPPED
[INFO] Apache Jena - Fuseki Embedded Server ............... SKIPPED
[INFO] Apache Jena - Fuseki WAR File ...................... SKIPPED
[INFO] Apache Jena - Fuseki Server Standalone Jar ......... SKIPPED
[INFO] Apache Jena - Fuseki Basic Server .................. SKIPPED
[INFO] Apache Jena - Fuseki Binary Distribution ........... SKIPPED
[INFO] Apache Jena - Integration Testing .................. SKIPPED
[INFO] Apache Jena - Distribution ......................... SKIPPED
[INFO] Apache Jena - Fuseki1 .............................. SKIPPED
[INFO] Apache Jena - Data Tables for RDF and SPARQL ....... SKIPPED
[INFO] Apache Jena - SDB (SQL based triple store) ......... SKIPPED
[INFO] Apache Jena - Security Permissions ................. SKIPPED
[INFO] Apache Jena - Extras ............................... SKIPPED
[INFO] Apache Jena - Extras - Query Builder ............... SKIPPED
[INFO] Apache Jena - JDBC Parent .......................... SKIPPED
[INFO] Apache Jena - JDBC Core API ........................ SKIPPED
[INFO] Apache Jena - JDBC Remote Endpoint Driver .......... SKIPPED
[INFO] Apache Jena - JDBC In-Memory Driver ................ SKIPPED
[INFO] Apache Jena - JDBC TDB Driver ...................... SKIPPED
[INFO] Apache Jena - JDBC Driver Bundle ................... SKIPPED
[INFO] Apache Jena - Elephas .............................. SKIPPED
[INFO] Apache Jena - Elephas - Common API ................. SKIPPED
[INFO] Apache Jena - Elephas - I/O ........................ SKIPPED
[INFO] Apache Jena - Elephas - Map/Reduce ................. SKIPPED
[INFO] Apache Jena - Elephas - Statistics Demo App ........ SKIPPED
[INFO] Apache Jena - OSGi ................................. SKIPPED
[INFO] Apache Jena - OSGi bundle .......................... SKIPPED
[INFO] Apache Jena - OSGi Karaf features 3.8.0-SNAPSHOT ... SKIPPED
[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 11.970 s
[INFO] Finished at: 2018-04-03T17:17:15+01:00
[INFO]
------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar (attach-javadocs)
on project jena-base: Execution attach-javadocs of goal
org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar failed.:
NullPointerException -> [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 :jena-base




On Tue, Apr 3, 2018 at 11:48 AM, Andy Seaborne <an...@apache.org> wrote:

> Semantic Versioning says nothing about source vs binary compatibility.
>
> The reason for having minor version normally is allow some evolution. Jena
> 3.7.0 is not a patch release.
>
> It is highlighted in "heads up" message to users@jena:
> https://lists.apache.org/thread.html/5b31a3b6794781f6a026586
> 08444043b5535957a6c94f3728efd8304@%3Cusers.jena.apache.org%3E
>
> What else do you want?
>
> We don't offer or test for binary compatibility (which would also include
> the binary compatibility of dependencies because apps may get them via
> depending on Jena). We don't claim drop-in replacement of jars either -
> exactly the opposite in fact. It causes users problems.
>
> >>>> ... but I would like the
> >>>> discussion held and consensus reached before the release goes ahead.
>
> That's rather vague.
>
> There was discussion on JENA-1389.
> What extra discussion?
>
> ----
>
> It seems me to be rather unhelpful to users to bump the major version
> number every time there is a binary change in any of our modules.  We are
> not Common components. Going back to version-per-module is unhelpful (users
> ignored it) as well.
>
>     Andy
>
>
> On 02/04/18 23:22, Claude Warren wrote:
>
>> I am not advocating that we create bridge methods in the  build as is
>> mentioned later in the linke I posted above, just asking about the proper
>> version numbers.
>>
>> Claude
>>
>> On Mon, Apr 2, 2018 at 11:20 PM, Claude Warren <cl...@xenei.com> wrote:
>>
>> Sorry, I should have included a link before:
>>>
>>> https://lists.apache.org/list.html?dev@commons.apache.org:
>>> lte=1M:%5Bcollections%5D%20breaking%20changes
>>>
>>>
>>>
>>> On Mon, Apr 2, 2018 at 11:02 AM, Andy Seaborne <an...@apache.org> wrote:
>>>
>>> Please see the discussions on the JIRA about source code compatibility.
>>>>
>>>> JENA-1389
>>>> https://github.com/apache/jena/pull/362
>>>>
>>>> JENA-1495
>>>> https://github.com/apache/jena/pull/368
>>>>
>>>> Where is that other discussion? A link would be helpful.
>>>>
>>>>      Andy
>>>>
>>>>
>>>> On 02/04/18 10:03, Claude Warren wrote:
>>>>
>>>> Should this not be released as a 4.0 version as I think we operate under
>>>>> semantic versioning and the API is not backwards compatible?
>>>>>
>>>>> There was a similar discussion over in Commons recently where several
>>>>> of
>>>>> the functions there were changed to return "this" rather than "void".
>>>>> Like
>>>>> our changes here.  The decision there was to revert those changes for
>>>>> the
>>>>> current release and place the "this" returning versions in the upcoming
>>>>> version number changing release.
>>>>>
>>>>> as noted in the Commons discussion:
>>>>>
>>>>> The return type is part of the method signature that Java uses to find
>>>>>
>>>>> resolve references.
>>>>>>
>>>>>> Even changing from void to non-void will cause binary incompatibility.
>>>>>> (Source-wise, that's fine)
>>>>>>
>>>>>>
>>>>>> I am not certain that I should vote -1 on this issue but I would like
>>>>> the
>>>>> discussion held and consensus reached before the release goes ahead.
>>>>>
>>>>> Claude
>>>>>
>>>>> On Sun, Apr 1, 2018 at 11:03 PM, ajs6f <aj...@apache.org> wrote:
>>>>>
>>>>> Please vote to approve this release:
>>>>>
>>>>>>
>>>>>>>         [ ] +1 Approve the release
>>>>>>>
>>>>>>>
>>>>>> +1
>>>>>>
>>>>>>         [ ]  0 Don't care
>>>>>>
>>>>>>>         [ ] -1 Don't release, because ...
>>>>>>>
>>>>>>>
>>>>>> + does everything work on OS X?
>>>>>>
>>>>>>>
>>>>>>>
>>>>>> Yes.
>>>>>>
>>>>>> + are the GPG signatures fine?
>>>>>>
>>>>>>>
>>>>>>>
>>>>>> Yes.
>>>>>>
>>>>>> + is there a source archive?
>>>>>>
>>>>>>>
>>>>>>>
>>>>>> Yes.
>>>>>>
>>>>>> + can the source archive really be built?
>>>>>>
>>>>>>>
>>>>>>>
>>>>>> Yes.
>>>>>>
>>>>>> ajs6f
>>>>>>
>>>>>> On Mar 29, 2018, at 2:28 PM, Andy Seaborne <an...@apache.org> wrote:
>>>>>>
>>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> Here is a vote on a release of Jena 3.7.0.
>>>>>>>
>>>>>>> This is the first proposed candidate for a 3.7.0 release.
>>>>>>>
>>>>>>> There are process changes.
>>>>>>>
>>>>>>> Deadline:
>>>>>>>
>>>>>>>         2018-04-01 22:00 UTC
>>>>>>>
>>>>>>> April 1st!
>>>>>>>
>>>>>>> ==== Process Changes
>>>>>>>
>>>>>>> 1/
>>>>>>> MD5 files are being discouraged because MD5 is not secure.  Projects
>>>>>>> are
>>>>>>>
>>>>>>> now asked to not publish md5.
>>>>>>
>>>>>>
>>>>>>> There are no md5 files in the proposed dist/jena area - files on
>>>>>>> Apache
>>>>>>>
>>>>>>> hardware.
>>>>>>
>>>>>>
>>>>>>> There are sha1 and sha512 checksums.
>>>>>>> * The sha512 is in Linux sha512sum checkable format.
>>>>>>> * The sha1 is whatever maven generated and is the same as will go to
>>>>>>>
>>>>>>> maven central.
>>>>>>
>>>>>>
>>>>>>> Having the sha1 ties the dist/jena artifacts to maven central (as
>>>>>>> does
>>>>>>>
>>>>>>> the .asc).
>>>>>>
>>>>>>
>>>>>>> There are md5 and sha1 in the proposes maven repo staging area for
>>>>>>>
>>>>>>> sending to maven central. That part of maven is hardwired to md5/sha1
>>>>>> still.
>>>>>>
>>>>>>
>>>>>>> There's a script to setup the sha512.
>>>>>>>
>>>>>>> 2/
>>>>>>> To establish the proof chain for signed artifacts in /dist/project/,
>>>>>>> I
>>>>>>>
>>>>>>> have been asked to try out the new META files.
>>>>>>
>>>>>>
>>>>>>> https://checker.apache.org/doc/README.html#ch-meta
>>>>>>>
>>>>>>> There are two files
>>>>>>>
>>>>>>> /dist/jena/META
>>>>>>> /dist/jena/META.asc
>>>>>>>
>>>>>>> META says who signs what, and is itself signed by the PMC chair.
>>>>>>>
>>>>>>> ==== Release changes
>>>>>>>
>>>>>>> 55 JIRA:
>>>>>>> https://s.apache.org/jena-3.7.0-jira
>>>>>>>
>>>>>>> == Significant Changes
>>>>>>>
>>>>>>> ** Java9: Building and running on a Java9 platform is supported
>>>>>>>
>>>>>>> JENA-1461 - Allow ARQ custom functions to be written in JavaScript
>>>>>>>
>>>>>>> JENA-1389 - Return `this` rather than `void` from Dataset (API
>>>>>>> change)
>>>>>>> JENA-1495 - Return Model from PrefixMapping methods (API change)
>>>>>>>
>>>>>>> JENA-1458, JENA-1483 - Transaction Promotion
>>>>>>>
>>>>>>> JENA-1453 - Lucene indexes using a graph field are smaller
>>>>>>>
>>>>>>> JENA-1490 - Working with Blank Nodes with Fuseki
>>>>>>>
>>>>>>> == Upgrades to libraries (runtime dependencies):
>>>>>>>
>>>>>>> No dependency changes.
>>>>>>>
>>>>>>> ==== Release Vote
>>>>>>>
>>>>>>> Everyone, not just committers, is invited to test and vote.
>>>>>>> Please download and test the proposed release.
>>>>>>>
>>>>>>> Proposed dist/ area:
>>>>>>>    https://dist.apache.org/repos/dist/dev/jena/
>>>>>>>
>>>>>>> Keys:
>>>>>>>    https://svn.apache.org/repos/asf/jena/dist/KEYS
>>>>>>>
>>>>>>> Staging repository:
>>>>>>>    https://repository.apache.org/content/repositories/orgapache
>>>>>>> jena-1022/
>>>>>>>
>>>>>>> Git commit (browser URL):
>>>>>>> https://git1-us-west.apache.org/repos/asf?p=jena.git;a=commi
>>>>>>> t;h=d4e7063e
>>>>>>>
>>>>>>> Git Commit Hash:
>>>>>>>    d4e7063e7a6db8ce77699bd0388e1a1bd6816626
>>>>>>>
>>>>>>> Git Commit Tag:
>>>>>>>       jena-3.7.0-rc1
>>>>>>>
>>>>>>> Please vote to approve this release:
>>>>>>>
>>>>>>>         [ ] +1 Approve the release
>>>>>>>         [ ]  0 Don't care
>>>>>>>         [ ] -1 Don't release, because ...
>>>>>>>
>>>>>>> This vote will be open until at least
>>>>>>>
>>>>>>>         2018-04-01 22:00 UTC
>>>>>>>
>>>>>>> If you expect to check the release but the time 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?
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>
>>> --
>>> I like: Like Like - The likeliest place on the web
>>> <http://like-like.xenei.com>
>>> LinkedIn: http://www.linkedin.com/in/claudewarren
>>>
>>>
>>
>>
>>


-- 
I like: Like Like - The likeliest place on the web
<http://like-like.xenei.com>
LinkedIn: http://www.linkedin.com/in/claudewarren

Re: [] Apache Jena 3.7.0 RC1

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

Semantic Versioning says nothing about source vs binary compatibility.

The reason for having minor version normally is allow some evolution. 
Jena 3.7.0 is not a patch release.

It is highlighted in "heads up" message to users@jena:
https://lists.apache.org/thread.html/5b31a3b6794781f6a02658608444043b5535957a6c94f3728efd8304@%3Cusers.jena.apache.org%3E

What else do you want?

We don't offer or test for binary compatibility (which would also 
include the binary compatibility of dependencies because apps may get 
them via depending on Jena). We don't claim drop-in replacement of jars 
either - exactly the opposite in fact. It causes users problems.

 >>>> ... but I would like the
 >>>> discussion held and consensus reached before the release goes ahead.

That's rather vague.

There was discussion on JENA-1389.
What extra discussion?

----

It seems me to be rather unhelpful to users to bump the major version 
number every time there is a binary change in any of our modules.  We 
are not Common components. Going back to version-per-module is unhelpful 
(users ignored it) as well.

     Andy

On 02/04/18 23:22, Claude Warren wrote:
> I am not advocating that we create bridge methods in the  build as is
> mentioned later in the linke I posted above, just asking about the proper
> version numbers.
> 
> Claude
> 
> On Mon, Apr 2, 2018 at 11:20 PM, Claude Warren <cl...@xenei.com> wrote:
> 
>> Sorry, I should have included a link before:
>>
>> https://lists.apache.org/list.html?dev@commons.apache.org:
>> lte=1M:%5Bcollections%5D%20breaking%20changes
>>
>>
>>
>> On Mon, Apr 2, 2018 at 11:02 AM, Andy Seaborne <an...@apache.org> wrote:
>>
>>> Please see the discussions on the JIRA about source code compatibility.
>>>
>>> JENA-1389
>>> https://github.com/apache/jena/pull/362
>>>
>>> JENA-1495
>>> https://github.com/apache/jena/pull/368
>>>
>>> Where is that other discussion? A link would be helpful.
>>>
>>>      Andy
>>>
>>>
>>> On 02/04/18 10:03, Claude Warren wrote:
>>>
>>>> Should this not be released as a 4.0 version as I think we operate under
>>>> semantic versioning and the API is not backwards compatible?
>>>>
>>>> There was a similar discussion over in Commons recently where several of
>>>> the functions there were changed to return "this" rather than "void".
>>>> Like
>>>> our changes here.  The decision there was to revert those changes for the
>>>> current release and place the "this" returning versions in the upcoming
>>>> version number changing release.
>>>>
>>>> as noted in the Commons discussion:
>>>>
>>>> The return type is part of the method signature that Java uses to find
>>>>
>>>>> resolve references.
>>>>>
>>>>> Even changing from void to non-void will cause binary incompatibility.
>>>>> (Source-wise, that's fine)
>>>>>
>>>>>
>>>> I am not certain that I should vote -1 on this issue but I would like the
>>>> discussion held and consensus reached before the release goes ahead.
>>>>
>>>> Claude
>>>>
>>>> On Sun, Apr 1, 2018 at 11:03 PM, ajs6f <aj...@apache.org> wrote:
>>>>
>>>> Please vote to approve this release:
>>>>>>
>>>>>>         [ ] +1 Approve the release
>>>>>>
>>>>>
>>>>> +1
>>>>>
>>>>>         [ ]  0 Don't care
>>>>>>         [ ] -1 Don't release, because ...
>>>>>>
>>>>>
>>>>> + does everything work on OS X?
>>>>>>
>>>>>
>>>>> Yes.
>>>>>
>>>>> + are the GPG signatures fine?
>>>>>>
>>>>>
>>>>> Yes.
>>>>>
>>>>> + is there a source archive?
>>>>>>
>>>>>
>>>>> Yes.
>>>>>
>>>>> + can the source archive really be built?
>>>>>>
>>>>>
>>>>> Yes.
>>>>>
>>>>> ajs6f
>>>>>
>>>>> On Mar 29, 2018, at 2:28 PM, Andy Seaborne <an...@apache.org> wrote:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> Here is a vote on a release of Jena 3.7.0.
>>>>>>
>>>>>> This is the first proposed candidate for a 3.7.0 release.
>>>>>>
>>>>>> There are process changes.
>>>>>>
>>>>>> Deadline:
>>>>>>
>>>>>>         2018-04-01 22:00 UTC
>>>>>>
>>>>>> April 1st!
>>>>>>
>>>>>> ==== Process Changes
>>>>>>
>>>>>> 1/
>>>>>> MD5 files are being discouraged because MD5 is not secure.  Projects
>>>>>> are
>>>>>>
>>>>> now asked to not publish md5.
>>>>>
>>>>>>
>>>>>> There are no md5 files in the proposed dist/jena area - files on Apache
>>>>>>
>>>>> hardware.
>>>>>
>>>>>>
>>>>>> There are sha1 and sha512 checksums.
>>>>>> * The sha512 is in Linux sha512sum checkable format.
>>>>>> * The sha1 is whatever maven generated and is the same as will go to
>>>>>>
>>>>> maven central.
>>>>>
>>>>>>
>>>>>> Having the sha1 ties the dist/jena artifacts to maven central (as does
>>>>>>
>>>>> the .asc).
>>>>>
>>>>>>
>>>>>> There are md5 and sha1 in the proposes maven repo staging area for
>>>>>>
>>>>> sending to maven central. That part of maven is hardwired to md5/sha1
>>>>> still.
>>>>>
>>>>>>
>>>>>> There's a script to setup the sha512.
>>>>>>
>>>>>> 2/
>>>>>> To establish the proof chain for signed artifacts in /dist/project/, I
>>>>>>
>>>>> have been asked to try out the new META files.
>>>>>
>>>>>>
>>>>>> https://checker.apache.org/doc/README.html#ch-meta
>>>>>>
>>>>>> There are two files
>>>>>>
>>>>>> /dist/jena/META
>>>>>> /dist/jena/META.asc
>>>>>>
>>>>>> META says who signs what, and is itself signed by the PMC chair.
>>>>>>
>>>>>> ==== Release changes
>>>>>>
>>>>>> 55 JIRA:
>>>>>> https://s.apache.org/jena-3.7.0-jira
>>>>>>
>>>>>> == Significant Changes
>>>>>>
>>>>>> ** Java9: Building and running on a Java9 platform is supported
>>>>>>
>>>>>> JENA-1461 - Allow ARQ custom functions to be written in JavaScript
>>>>>>
>>>>>> JENA-1389 - Return `this` rather than `void` from Dataset (API change)
>>>>>> JENA-1495 - Return Model from PrefixMapping methods (API change)
>>>>>>
>>>>>> JENA-1458, JENA-1483 - Transaction Promotion
>>>>>>
>>>>>> JENA-1453 - Lucene indexes using a graph field are smaller
>>>>>>
>>>>>> JENA-1490 - Working with Blank Nodes with Fuseki
>>>>>>
>>>>>> == Upgrades to libraries (runtime dependencies):
>>>>>>
>>>>>> No dependency changes.
>>>>>>
>>>>>> ==== Release Vote
>>>>>>
>>>>>> Everyone, not just committers, is invited to test and vote.
>>>>>> Please download and test the proposed release.
>>>>>>
>>>>>> Proposed dist/ area:
>>>>>>    https://dist.apache.org/repos/dist/dev/jena/
>>>>>>
>>>>>> Keys:
>>>>>>    https://svn.apache.org/repos/asf/jena/dist/KEYS
>>>>>>
>>>>>> Staging repository:
>>>>>>    https://repository.apache.org/content/repositories/orgapache
>>>>>> jena-1022/
>>>>>>
>>>>>> Git commit (browser URL):
>>>>>> https://git1-us-west.apache.org/repos/asf?p=jena.git;a=commi
>>>>>> t;h=d4e7063e
>>>>>>
>>>>>> Git Commit Hash:
>>>>>>    d4e7063e7a6db8ce77699bd0388e1a1bd6816626
>>>>>>
>>>>>> Git Commit Tag:
>>>>>>       jena-3.7.0-rc1
>>>>>>
>>>>>> Please vote to approve this release:
>>>>>>
>>>>>>         [ ] +1 Approve the release
>>>>>>         [ ]  0 Don't care
>>>>>>         [ ] -1 Don't release, because ...
>>>>>>
>>>>>> This vote will be open until at least
>>>>>>
>>>>>>         2018-04-01 22:00 UTC
>>>>>>
>>>>>> If you expect to check the release but the time 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?
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>
>>
>> --
>> I like: Like Like - The likeliest place on the web
>> <http://like-like.xenei.com>
>> LinkedIn: http://www.linkedin.com/in/claudewarren
>>
> 
> 
>

Re: [VOTE] Apache Jena 3.7.0 RC1

Posted by Claude Warren <cl...@xenei.com>.

I am not advocating that we create bridge methods in the  build as is
mentioned later in the linke I posted above, just asking about the proper
version numbers.

Claude

On Mon, Apr 2, 2018 at 11:20 PM, Claude Warren <cl...@xenei.com> wrote:

> Sorry, I should have included a link before:
>
> https://lists.apache.org/list.html?dev@commons.apache.org:
> lte=1M:%5Bcollections%5D%20breaking%20changes
>
>
>
> On Mon, Apr 2, 2018 at 11:02 AM, Andy Seaborne <an...@apache.org> wrote:
>
>> Please see the discussions on the JIRA about source code compatibility.
>>
>> JENA-1389
>> https://github.com/apache/jena/pull/362
>>
>> JENA-1495
>> https://github.com/apache/jena/pull/368
>>
>> Where is that other discussion? A link would be helpful.
>>
>>     Andy
>>
>>
>> On 02/04/18 10:03, Claude Warren wrote:
>>
>>> Should this not be released as a 4.0 version as I think we operate under
>>> semantic versioning and the API is not backwards compatible?
>>>
>>> There was a similar discussion over in Commons recently where several of
>>> the functions there were changed to return "this" rather than "void".
>>> Like
>>> our changes here.  The decision there was to revert those changes for the
>>> current release and place the "this" returning versions in the upcoming
>>> version number changing release.
>>>
>>> as noted in the Commons discussion:
>>>
>>> The return type is part of the method signature that Java uses to find
>>>
>>>> resolve references.
>>>>
>>>> Even changing from void to non-void will cause binary incompatibility.
>>>> (Source-wise, that's fine)
>>>>
>>>>
>>> I am not certain that I should vote -1 on this issue but I would like the
>>> discussion held and consensus reached before the release goes ahead.
>>>
>>> Claude
>>>
>>> On Sun, Apr 1, 2018 at 11:03 PM, ajs6f <aj...@apache.org> wrote:
>>>
>>> Please vote to approve this release:
>>>>>
>>>>>        [ ] +1 Approve the release
>>>>>
>>>>
>>>> +1
>>>>
>>>>        [ ]  0 Don't care
>>>>>        [ ] -1 Don't release, because ...
>>>>>
>>>>
>>>> + does everything work on OS X?
>>>>>
>>>>
>>>> Yes.
>>>>
>>>> + are the GPG signatures fine?
>>>>>
>>>>
>>>> Yes.
>>>>
>>>> + is there a source archive?
>>>>>
>>>>
>>>> Yes.
>>>>
>>>> + can the source archive really be built?
>>>>>
>>>>
>>>> Yes.
>>>>
>>>> ajs6f
>>>>
>>>> On Mar 29, 2018, at 2:28 PM, Andy Seaborne <an...@apache.org> wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> Here is a vote on a release of Jena 3.7.0.
>>>>>
>>>>> This is the first proposed candidate for a 3.7.0 release.
>>>>>
>>>>> There are process changes.
>>>>>
>>>>> Deadline:
>>>>>
>>>>>        2018-04-01 22:00 UTC
>>>>>
>>>>> April 1st!
>>>>>
>>>>> ==== Process Changes
>>>>>
>>>>> 1/
>>>>> MD5 files are being discouraged because MD5 is not secure.  Projects
>>>>> are
>>>>>
>>>> now asked to not publish md5.
>>>>
>>>>>
>>>>> There are no md5 files in the proposed dist/jena area - files on Apache
>>>>>
>>>> hardware.
>>>>
>>>>>
>>>>> There are sha1 and sha512 checksums.
>>>>> * The sha512 is in Linux sha512sum checkable format.
>>>>> * The sha1 is whatever maven generated and is the same as will go to
>>>>>
>>>> maven central.
>>>>
>>>>>
>>>>> Having the sha1 ties the dist/jena artifacts to maven central (as does
>>>>>
>>>> the .asc).
>>>>
>>>>>
>>>>> There are md5 and sha1 in the proposes maven repo staging area for
>>>>>
>>>> sending to maven central. That part of maven is hardwired to md5/sha1
>>>> still.
>>>>
>>>>>
>>>>> There's a script to setup the sha512.
>>>>>
>>>>> 2/
>>>>> To establish the proof chain for signed artifacts in /dist/project/, I
>>>>>
>>>> have been asked to try out the new META files.
>>>>
>>>>>
>>>>> https://checker.apache.org/doc/README.html#ch-meta
>>>>>
>>>>> There are two files
>>>>>
>>>>> /dist/jena/META
>>>>> /dist/jena/META.asc
>>>>>
>>>>> META says who signs what, and is itself signed by the PMC chair.
>>>>>
>>>>> ==== Release changes
>>>>>
>>>>> 55 JIRA:
>>>>> https://s.apache.org/jena-3.7.0-jira
>>>>>
>>>>> == Significant Changes
>>>>>
>>>>> ** Java9: Building and running on a Java9 platform is supported
>>>>>
>>>>> JENA-1461 - Allow ARQ custom functions to be written in JavaScript
>>>>>
>>>>> JENA-1389 - Return `this` rather than `void` from Dataset (API change)
>>>>> JENA-1495 - Return Model from PrefixMapping methods (API change)
>>>>>
>>>>> JENA-1458, JENA-1483 - Transaction Promotion
>>>>>
>>>>> JENA-1453 - Lucene indexes using a graph field are smaller
>>>>>
>>>>> JENA-1490 - Working with Blank Nodes with Fuseki
>>>>>
>>>>> == Upgrades to libraries (runtime dependencies):
>>>>>
>>>>> No dependency changes.
>>>>>
>>>>> ==== Release Vote
>>>>>
>>>>> Everyone, not just committers, is invited to test and vote.
>>>>> Please download and test the proposed release.
>>>>>
>>>>> Proposed dist/ area:
>>>>>   https://dist.apache.org/repos/dist/dev/jena/
>>>>>
>>>>> Keys:
>>>>>   https://svn.apache.org/repos/asf/jena/dist/KEYS
>>>>>
>>>>> Staging repository:
>>>>>   https://repository.apache.org/content/repositories/orgapache
>>>>> jena-1022/
>>>>>
>>>>> Git commit (browser URL):
>>>>> https://git1-us-west.apache.org/repos/asf?p=jena.git;a=commi
>>>>> t;h=d4e7063e
>>>>>
>>>>> Git Commit Hash:
>>>>>   d4e7063e7a6db8ce77699bd0388e1a1bd6816626
>>>>>
>>>>> Git Commit Tag:
>>>>>      jena-3.7.0-rc1
>>>>>
>>>>> Please vote to approve this release:
>>>>>
>>>>>        [ ] +1 Approve the release
>>>>>        [ ]  0 Don't care
>>>>>        [ ] -1 Don't release, because ...
>>>>>
>>>>> This vote will be open until at least
>>>>>
>>>>>        2018-04-01 22:00 UTC
>>>>>
>>>>> If you expect to check the release but the time 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?
>>>>>
>>>>
>>>>
>>>>
>>>
>>>
>
>
> --
> I like: Like Like - The likeliest place on the web
> <http://like-like.xenei.com>
> LinkedIn: http://www.linkedin.com/in/claudewarren
>



-- 
I like: Like Like - The likeliest place on the web
<http://like-like.xenei.com>
LinkedIn: http://www.linkedin.com/in/claudewarren

Re: [VOTE] Apache Jena 3.7.0 RC1

Posted by Claude Warren <cl...@xenei.com>.

Sorry, I should have included a link before:

https://lists.apache.org/list.html?dev@commons.apache.org:lte=1M:%5Bcollections%5D%20breaking%20changes



On Mon, Apr 2, 2018 at 11:02 AM, Andy Seaborne <an...@apache.org> wrote:

> Please see the discussions on the JIRA about source code compatibility.
>
> JENA-1389
> https://github.com/apache/jena/pull/362
>
> JENA-1495
> https://github.com/apache/jena/pull/368
>
> Where is that other discussion? A link would be helpful.
>
>     Andy
>
>
> On 02/04/18 10:03, Claude Warren wrote:
>
>> Should this not be released as a 4.0 version as I think we operate under
>> semantic versioning and the API is not backwards compatible?
>>
>> There was a similar discussion over in Commons recently where several of
>> the functions there were changed to return "this" rather than "void". Like
>> our changes here.  The decision there was to revert those changes for the
>> current release and place the "this" returning versions in the upcoming
>> version number changing release.
>>
>> as noted in the Commons discussion:
>>
>> The return type is part of the method signature that Java uses to find
>>
>>> resolve references.
>>>
>>> Even changing from void to non-void will cause binary incompatibility.
>>> (Source-wise, that's fine)
>>>
>>>
>> I am not certain that I should vote -1 on this issue but I would like the
>> discussion held and consensus reached before the release goes ahead.
>>
>> Claude
>>
>> On Sun, Apr 1, 2018 at 11:03 PM, ajs6f <aj...@apache.org> wrote:
>>
>> Please vote to approve this release:
>>>>
>>>>        [ ] +1 Approve the release
>>>>
>>>
>>> +1
>>>
>>>        [ ]  0 Don't care
>>>>        [ ] -1 Don't release, because ...
>>>>
>>>
>>> + does everything work on OS X?
>>>>
>>>
>>> Yes.
>>>
>>> + are the GPG signatures fine?
>>>>
>>>
>>> Yes.
>>>
>>> + is there a source archive?
>>>>
>>>
>>> Yes.
>>>
>>> + can the source archive really be built?
>>>>
>>>
>>> Yes.
>>>
>>> ajs6f
>>>
>>> On Mar 29, 2018, at 2:28 PM, Andy Seaborne <an...@apache.org> wrote:
>>>>
>>>> Hi,
>>>>
>>>> Here is a vote on a release of Jena 3.7.0.
>>>>
>>>> This is the first proposed candidate for a 3.7.0 release.
>>>>
>>>> There are process changes.
>>>>
>>>> Deadline:
>>>>
>>>>        2018-04-01 22:00 UTC
>>>>
>>>> April 1st!
>>>>
>>>> ==== Process Changes
>>>>
>>>> 1/
>>>> MD5 files are being discouraged because MD5 is not secure.  Projects are
>>>>
>>> now asked to not publish md5.
>>>
>>>>
>>>> There are no md5 files in the proposed dist/jena area - files on Apache
>>>>
>>> hardware.
>>>
>>>>
>>>> There are sha1 and sha512 checksums.
>>>> * The sha512 is in Linux sha512sum checkable format.
>>>> * The sha1 is whatever maven generated and is the same as will go to
>>>>
>>> maven central.
>>>
>>>>
>>>> Having the sha1 ties the dist/jena artifacts to maven central (as does
>>>>
>>> the .asc).
>>>
>>>>
>>>> There are md5 and sha1 in the proposes maven repo staging area for
>>>>
>>> sending to maven central. That part of maven is hardwired to md5/sha1
>>> still.
>>>
>>>>
>>>> There's a script to setup the sha512.
>>>>
>>>> 2/
>>>> To establish the proof chain for signed artifacts in /dist/project/, I
>>>>
>>> have been asked to try out the new META files.
>>>
>>>>
>>>> https://checker.apache.org/doc/README.html#ch-meta
>>>>
>>>> There are two files
>>>>
>>>> /dist/jena/META
>>>> /dist/jena/META.asc
>>>>
>>>> META says who signs what, and is itself signed by the PMC chair.
>>>>
>>>> ==== Release changes
>>>>
>>>> 55 JIRA:
>>>> https://s.apache.org/jena-3.7.0-jira
>>>>
>>>> == Significant Changes
>>>>
>>>> ** Java9: Building and running on a Java9 platform is supported
>>>>
>>>> JENA-1461 - Allow ARQ custom functions to be written in JavaScript
>>>>
>>>> JENA-1389 - Return `this` rather than `void` from Dataset (API change)
>>>> JENA-1495 - Return Model from PrefixMapping methods (API change)
>>>>
>>>> JENA-1458, JENA-1483 - Transaction Promotion
>>>>
>>>> JENA-1453 - Lucene indexes using a graph field are smaller
>>>>
>>>> JENA-1490 - Working with Blank Nodes with Fuseki
>>>>
>>>> == Upgrades to libraries (runtime dependencies):
>>>>
>>>> No dependency changes.
>>>>
>>>> ==== Release Vote
>>>>
>>>> Everyone, not just committers, is invited to test and vote.
>>>> Please download and test the proposed release.
>>>>
>>>> Proposed dist/ area:
>>>>   https://dist.apache.org/repos/dist/dev/jena/
>>>>
>>>> Keys:
>>>>   https://svn.apache.org/repos/asf/jena/dist/KEYS
>>>>
>>>> Staging repository:
>>>>   https://repository.apache.org/content/repositories/orgapache
>>>> jena-1022/
>>>>
>>>> Git commit (browser URL):
>>>> https://git1-us-west.apache.org/repos/asf?p=jena.git;a=commi
>>>> t;h=d4e7063e
>>>>
>>>> Git Commit Hash:
>>>>   d4e7063e7a6db8ce77699bd0388e1a1bd6816626
>>>>
>>>> Git Commit Tag:
>>>>      jena-3.7.0-rc1
>>>>
>>>> Please vote to approve this release:
>>>>
>>>>        [ ] +1 Approve the release
>>>>        [ ]  0 Don't care
>>>>        [ ] -1 Don't release, because ...
>>>>
>>>> This vote will be open until at least
>>>>
>>>>        2018-04-01 22:00 UTC
>>>>
>>>> If you expect to check the release but the time 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?
>>>>
>>>
>>>
>>>
>>
>>


-- 
I like: Like Like - The likeliest place on the web
<http://like-like.xenei.com>
LinkedIn: http://www.linkedin.com/in/claudewarren

Re: [VOTE] Apache Jena 3.7.0 RC1

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

Please see the discussions on the JIRA about source code compatibility.

JENA-1389
https://github.com/apache/jena/pull/362

JENA-1495
https://github.com/apache/jena/pull/368

Where is that other discussion? A link would be helpful.

     Andy

On 02/04/18 10:03, Claude Warren wrote:
> Should this not be released as a 4.0 version as I think we operate under
> semantic versioning and the API is not backwards compatible?
> 
> There was a similar discussion over in Commons recently where several of
> the functions there were changed to return "this" rather than "void". Like
> our changes here.  The decision there was to revert those changes for the
> current release and place the "this" returning versions in the upcoming
> version number changing release.
> 
> as noted in the Commons discussion:
> 
> The return type is part of the method signature that Java uses to find
>> resolve references.
>>
>> Even changing from void to non-void will cause binary incompatibility.
>> (Source-wise, that's fine)
>>
> 
> I am not certain that I should vote -1 on this issue but I would like the
> discussion held and consensus reached before the release goes ahead.
> 
> Claude
> 
> On Sun, Apr 1, 2018 at 11:03 PM, ajs6f <aj...@apache.org> wrote:
> 
>>> Please vote to approve this release:
>>>
>>>        [ ] +1 Approve the release
>>
>> +1
>>
>>>        [ ]  0 Don't care
>>>        [ ] -1 Don't release, because ...
>>
>>> + does everything work on OS X?
>>
>> Yes.
>>
>>> + are the GPG signatures fine?
>>
>> Yes.
>>
>>> + is there a source archive?
>>
>> Yes.
>>
>>> + can the source archive really be built?
>>
>> Yes.
>>
>> ajs6f
>>
>>> On Mar 29, 2018, at 2:28 PM, Andy Seaborne <an...@apache.org> wrote:
>>>
>>> Hi,
>>>
>>> Here is a vote on a release of Jena 3.7.0.
>>>
>>> This is the first proposed candidate for a 3.7.0 release.
>>>
>>> There are process changes.
>>>
>>> Deadline:
>>>
>>>        2018-04-01 22:00 UTC
>>>
>>> April 1st!
>>>
>>> ==== Process Changes
>>>
>>> 1/
>>> MD5 files are being discouraged because MD5 is not secure.  Projects are
>> now asked to not publish md5.
>>>
>>> There are no md5 files in the proposed dist/jena area - files on Apache
>> hardware.
>>>
>>> There are sha1 and sha512 checksums.
>>> * The sha512 is in Linux sha512sum checkable format.
>>> * The sha1 is whatever maven generated and is the same as will go to
>> maven central.
>>>
>>> Having the sha1 ties the dist/jena artifacts to maven central (as does
>> the .asc).
>>>
>>> There are md5 and sha1 in the proposes maven repo staging area for
>> sending to maven central. That part of maven is hardwired to md5/sha1 still.
>>>
>>> There's a script to setup the sha512.
>>>
>>> 2/
>>> To establish the proof chain for signed artifacts in /dist/project/, I
>> have been asked to try out the new META files.
>>>
>>> https://checker.apache.org/doc/README.html#ch-meta
>>>
>>> There are two files
>>>
>>> /dist/jena/META
>>> /dist/jena/META.asc
>>>
>>> META says who signs what, and is itself signed by the PMC chair.
>>>
>>> ==== Release changes
>>>
>>> 55 JIRA:
>>> https://s.apache.org/jena-3.7.0-jira
>>>
>>> == Significant Changes
>>>
>>> ** Java9: Building and running on a Java9 platform is supported
>>>
>>> JENA-1461 - Allow ARQ custom functions to be written in JavaScript
>>>
>>> JENA-1389 - Return `this` rather than `void` from Dataset (API change)
>>> JENA-1495 - Return Model from PrefixMapping methods (API change)
>>>
>>> JENA-1458, JENA-1483 - Transaction Promotion
>>>
>>> JENA-1453 - Lucene indexes using a graph field are smaller
>>>
>>> JENA-1490 - Working with Blank Nodes with Fuseki
>>>
>>> == Upgrades to libraries (runtime dependencies):
>>>
>>> No dependency changes.
>>>
>>> ==== Release Vote
>>>
>>> Everyone, not just committers, is invited to test and vote.
>>> Please download and test the proposed release.
>>>
>>> Proposed dist/ area:
>>>   https://dist.apache.org/repos/dist/dev/jena/
>>>
>>> Keys:
>>>   https://svn.apache.org/repos/asf/jena/dist/KEYS
>>>
>>> Staging repository:
>>>   https://repository.apache.org/content/repositories/orgapachejena-1022/
>>>
>>> Git commit (browser URL):
>>> https://git1-us-west.apache.org/repos/asf?p=jena.git;a=commit;h=d4e7063e
>>>
>>> Git Commit Hash:
>>>   d4e7063e7a6db8ce77699bd0388e1a1bd6816626
>>>
>>> Git Commit Tag:
>>>      jena-3.7.0-rc1
>>>
>>> Please vote to approve this release:
>>>
>>>        [ ] +1 Approve the release
>>>        [ ]  0 Don't care
>>>        [ ] -1 Don't release, because ...
>>>
>>> This vote will be open until at least
>>>
>>>        2018-04-01 22:00 UTC
>>>
>>> If you expect to check the release but the time 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] Apache Jena 3.7.0 RC1

Posted by Claude Warren <cl...@xenei.com>.

Should this not be released as a 4.0 version as I think we operate under
semantic versioning and the API is not backwards compatible?

There was a similar discussion over in Commons recently where several of
the functions there were changed to return "this" rather than "void". Like
our changes here.  The decision there was to revert those changes for the
current release and place the "this" returning versions in the upcoming
version number changing release.

as noted in the Commons discussion:

The return type is part of the method signature that Java uses to find
> resolve references.
>
> Even changing from void to non-void will cause binary incompatibility.
> (Source-wise, that's fine)
>

I am not certain that I should vote -1 on this issue but I would like the
discussion held and consensus reached before the release goes ahead.

Claude

On Sun, Apr 1, 2018 at 11:03 PM, ajs6f <aj...@apache.org> wrote:

> > Please vote to approve this release:
> >
> >       [ ] +1 Approve the release
>
> +1
>
> >       [ ]  0 Don't care
> >       [ ] -1 Don't release, because ...
>
> > + does everything work on OS X?
>
> Yes.
>
> > + are the GPG signatures fine?
>
> Yes.
>
> > + is there a source archive?
>
> Yes.
>
> > + can the source archive really be built?
>
> Yes.
>
> ajs6f
>
> > On Mar 29, 2018, at 2:28 PM, Andy Seaborne <an...@apache.org> wrote:
> >
> > Hi,
> >
> > Here is a vote on a release of Jena 3.7.0.
> >
> > This is the first proposed candidate for a 3.7.0 release.
> >
> > There are process changes.
> >
> > Deadline:
> >
> >       2018-04-01 22:00 UTC
> >
> > April 1st!
> >
> > ==== Process Changes
> >
> > 1/
> > MD5 files are being discouraged because MD5 is not secure.  Projects are
> now asked to not publish md5.
> >
> > There are no md5 files in the proposed dist/jena area - files on Apache
> hardware.
> >
> > There are sha1 and sha512 checksums.
> > * The sha512 is in Linux sha512sum checkable format.
> > * The sha1 is whatever maven generated and is the same as will go to
> maven central.
> >
> > Having the sha1 ties the dist/jena artifacts to maven central (as does
> the .asc).
> >
> > There are md5 and sha1 in the proposes maven repo staging area for
> sending to maven central. That part of maven is hardwired to md5/sha1 still.
> >
> > There's a script to setup the sha512.
> >
> > 2/
> > To establish the proof chain for signed artifacts in /dist/project/, I
> have been asked to try out the new META files.
> >
> > https://checker.apache.org/doc/README.html#ch-meta
> >
> > There are two files
> >
> > /dist/jena/META
> > /dist/jena/META.asc
> >
> > META says who signs what, and is itself signed by the PMC chair.
> >
> > ==== Release changes
> >
> > 55 JIRA:
> > https://s.apache.org/jena-3.7.0-jira
> >
> > == Significant Changes
> >
> > ** Java9: Building and running on a Java9 platform is supported
> >
> > JENA-1461 - Allow ARQ custom functions to be written in JavaScript
> >
> > JENA-1389 - Return `this` rather than `void` from Dataset (API change)
> > JENA-1495 - Return Model from PrefixMapping methods (API change)
> >
> > JENA-1458, JENA-1483 - Transaction Promotion
> >
> > JENA-1453 - Lucene indexes using a graph field are smaller
> >
> > JENA-1490 - Working with Blank Nodes with Fuseki
> >
> > == Upgrades to libraries (runtime dependencies):
> >
> > No dependency changes.
> >
> > ==== Release Vote
> >
> > Everyone, not just committers, is invited to test and vote.
> > Please download and test the proposed release.
> >
> > Proposed dist/ area:
> >  https://dist.apache.org/repos/dist/dev/jena/
> >
> > Keys:
> >  https://svn.apache.org/repos/asf/jena/dist/KEYS
> >
> > Staging repository:
> >  https://repository.apache.org/content/repositories/orgapachejena-1022/
> >
> > Git commit (browser URL):
> > https://git1-us-west.apache.org/repos/asf?p=jena.git;a=commit;h=d4e7063e
> >
> > Git Commit Hash:
> >  d4e7063e7a6db8ce77699bd0388e1a1bd6816626
> >
> > Git Commit Tag:
> >     jena-3.7.0-rc1
> >
> > Please vote to approve this release:
> >
> >       [ ] +1 Approve the release
> >       [ ]  0 Don't care
> >       [ ] -1 Don't release, because ...
> >
> > This vote will be open until at least
> >
> >       2018-04-01 22:00 UTC
> >
> > If you expect to check the release but the time 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?
>
>


-- 
I like: Like Like - The likeliest place on the web
<http://like-like.xenei.com>
LinkedIn: http://www.linkedin.com/in/claudewarren

Re: [VOTE] Apache Jena 3.7.0 RC1

Posted by ajs6f <aj...@apache.org>.

> Please vote to approve this release:
> 
>       [ ] +1 Approve the release

+1

>       [ ]  0 Don't care
>       [ ] -1 Don't release, because ...

> + does everything work on OS X?

Yes.

> + are the GPG signatures fine?

Yes.

> + is there a source archive?

Yes.

> + can the source archive really be built?

Yes.

ajs6f

> On Mar 29, 2018, at 2:28 PM, Andy Seaborne <an...@apache.org> wrote:
> 
> Hi,
> 
> Here is a vote on a release of Jena 3.7.0.
> 
> This is the first proposed candidate for a 3.7.0 release.
> 
> There are process changes.
> 
> Deadline:
> 
>       2018-04-01 22:00 UTC
> 
> April 1st!
> 
> ==== Process Changes
> 
> 1/
> MD5 files are being discouraged because MD5 is not secure.  Projects are now asked to not publish md5.
> 
> There are no md5 files in the proposed dist/jena area - files on Apache hardware.
> 
> There are sha1 and sha512 checksums.
> * The sha512 is in Linux sha512sum checkable format.
> * The sha1 is whatever maven generated and is the same as will go to maven central.
> 
> Having the sha1 ties the dist/jena artifacts to maven central (as does the .asc).
> 
> There are md5 and sha1 in the proposes maven repo staging area for sending to maven central. That part of maven is hardwired to md5/sha1 still.
> 
> There's a script to setup the sha512.
> 
> 2/
> To establish the proof chain for signed artifacts in /dist/project/, I have been asked to try out the new META files.
> 
> https://checker.apache.org/doc/README.html#ch-meta
> 
> There are two files
> 
> /dist/jena/META
> /dist/jena/META.asc
> 
> META says who signs what, and is itself signed by the PMC chair.
> 
> ==== Release changes
> 
> 55 JIRA:
> https://s.apache.org/jena-3.7.0-jira
> 
> == Significant Changes
> 
> ** Java9: Building and running on a Java9 platform is supported
> 
> JENA-1461 - Allow ARQ custom functions to be written in JavaScript
> 
> JENA-1389 - Return `this` rather than `void` from Dataset (API change)
> JENA-1495 - Return Model from PrefixMapping methods (API change)
> 
> JENA-1458, JENA-1483 - Transaction Promotion
> 
> JENA-1453 - Lucene indexes using a graph field are smaller
> 
> JENA-1490 - Working with Blank Nodes with Fuseki
> 
> == Upgrades to libraries (runtime dependencies):
> 
> No dependency changes.
> 
> ==== Release Vote
> 
> Everyone, not just committers, is invited to test and vote.
> Please download and test the proposed release.
> 
> Proposed dist/ area:
>  https://dist.apache.org/repos/dist/dev/jena/
> 
> Keys:
>  https://svn.apache.org/repos/asf/jena/dist/KEYS
> 
> Staging repository:
>  https://repository.apache.org/content/repositories/orgapachejena-1022/
> 
> Git commit (browser URL):
> https://git1-us-west.apache.org/repos/asf?p=jena.git;a=commit;h=d4e7063e
> 
> Git Commit Hash:
>  d4e7063e7a6db8ce77699bd0388e1a1bd6816626
> 
> Git Commit Tag:
>     jena-3.7.0-rc1
> 
> Please vote to approve this release:
> 
>       [ ] +1 Approve the release
>       [ ]  0 Don't care
>       [ ] -1 Don't release, because ...
> 
> This vote will be open until at least
> 
>       2018-04-01 22:00 UTC
> 
> If you expect to check the release but the time 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: [] Apache Jena 3.7.0 RC1

Posted by Claude Warren <cl...@xenei.com>.

Sent report under RC2 issue.  I will take this conversation there.

On Thu, Apr 5, 2018 at 10:18 AM, Andy Seaborne <an...@apache.org> wrote:

> I grabbed the latest version of maven so as to run with exactly the same
> version of maven. Building current development (reset to 3.7.0-SNAPSHOT)
> worked for me.
>
> The javadoc doc for 3.7.0 is already loaded onto jena.staging.
>
> We now have 4 (if you include jenkins) independent reports of success.
>
> It must be quite frustrating but if there is a non-deterministic bug in
> the javadoc:attach-javadocs goal, there is not a lot we can do.
>
> The update to plugin-javadoc:3.0.0 was necessary to run with a Java9 JDK
> but you could try locally running with an earlier one.  (Or skip javadoc
> because it is on the web and can be downloaded in javadoc jars.)
>
> There is some recent stackoverflow foo that looks like it but it seems to
> be Java10 related.
>
>     Andy
>
>
> On 05/04/18 09:26, Claude Warren wrote:
>
>> Following up on the NPE I reported.  I switched to the original RC1 code
>> and had the same issue.
>>
>> Intiial run reported:
>> [INFO] --- maven-javadoc-plugin:3.0.0:jar (attach-javadocs) @ jena-base
>> ---
>> [INFO] The goal
>> 'org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:javadoc' has not
>> been
>> previously called for the module:
>> 'org.apache.jena:jena-shaded-guava:jar:3.7.0'. Trying to invoke it...
>> [WARNING] Creating fake javadoc directory to prevent repeated invocations:
>> /home/claude/git/jena/jena-shaded-guava/target/apidocs
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Reactor Summary:
>> [INFO]
>> [INFO] Apache Jena 3.7.0 .................................. SUCCESS [
>> 1.287 s]
>> [INFO] Apache Jena - Shadowed external libraries .......... SUCCESS [
>> 1.504 s]
>> [INFO] Apache Jena - IRI .................................. SUCCESS [
>> 2.575 s]
>> [INFO] Apache Jena - Base Common Environment .............. FAILURE [
>> 3.921 s]
>> [INFO] Apache Jena - Core ................................. SKIPPED
>> [INFO] Apache Jena - ARQ (SPARQL 1.1 Query Engine) ........ SKIPPED
>> [INFO] Apache Jena - RDF Connection ....................... SKIPPED
>> [INFO] Apache Jena - TDB1 (Native Triple Store) ........... SKIPPED
>> [INFO] Apache Jena - Database Operation Environment ....... SKIPPED
>> [INFO] Apache Jena - DBOE Base ............................ SKIPPED
>> [INFO] Apache Jena - DBOE Transactions .................... SKIPPED
>> [INFO] Apache Jena - DBOE Indexes ......................... SKIPPED
>> [INFO] Apache Jena - DBOE Index test suite ................ SKIPPED
>> [INFO] Apache Jena - DBOE Transactional Datastructures .... SKIPPED
>> [INFO] Apache Jena - TDB2 ................................. SKIPPED
>> [INFO] Apache Jena - Libraries POM ........................ SKIPPED
>> [INFO] Apache Jena - Command line tools ................... SKIPPED
>> [INFO] Apache Jena - SPARQL Text Search ................... SKIPPED
>> [INFO] Apache Jena - SPARQL Text Search - Elasticsearch ... SKIPPED
>> [INFO] Apache Jena - SPARQL Spatial Search ................ SKIPPED
>> [INFO] Apache Jena - Fuseki - A SPARQL 1.1 Server ......... SKIPPED
>> [INFO] Apache Jena - Fuseki Server Engine ................. SKIPPED
>> [INFO] Apache Jena - Fuseki Embedded Server ............... SKIPPED
>> [INFO] Apache Jena - Fuseki WAR File ...................... SKIPPED
>> [INFO] Apache Jena - Fuseki Server Standalone Jar ......... SKIPPED
>> [INFO] Apache Jena - Fuseki Basic Server .................. SKIPPED
>> [INFO] Apache Jena - Fuseki Binary Distribution ........... SKIPPED
>> [INFO] Apache Jena - Integration Testing .................. SKIPPED
>> [INFO] Apache Jena - Distribution ......................... SKIPPED
>> [INFO] Apache Jena - Fuseki1 .............................. SKIPPED
>> [INFO] Apache Jena - Data Tables for RDF and SPARQL ....... SKIPPED
>> [INFO] Apache Jena - SDB (SQL based triple store) ......... SKIPPED
>> [INFO] Apache Jena - Security Permissions ................. SKIPPED
>> [INFO] Apache Jena - Extras ............................... SKIPPED
>> [INFO] Apache Jena - Extras - Query Builder ............... SKIPPED
>> [INFO] Apache Jena - JDBC Parent .......................... SKIPPED
>> [INFO] Apache Jena - JDBC Core API ........................ SKIPPED
>> [INFO] Apache Jena - JDBC Remote Endpoint Driver .......... SKIPPED
>> [INFO] Apache Jena - JDBC In-Memory Driver ................ SKIPPED
>> [INFO] Apache Jena - JDBC TDB Driver ...................... SKIPPED
>> [INFO] Apache Jena - JDBC Driver Bundle ................... SKIPPED
>> [INFO] Apache Jena - Elephas .............................. SKIPPED
>> [INFO] Apache Jena - Elephas - Common API ................. SKIPPED
>> [INFO] Apache Jena - Elephas - I/O ........................ SKIPPED
>> [INFO] Apache Jena - Elephas - Map/Reduce ................. SKIPPED
>> [INFO] Apache Jena - Elephas - Statistics Demo App ........ SKIPPED
>> [INFO] Apache Jena - OSGi ................................. SKIPPED
>> [INFO] Apache Jena - OSGi bundle .......................... SKIPPED
>> [INFO] Apache Jena - OSGi Karaf features 3.7.0 ............ SKIPPED
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] BUILD FAILURE
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Total time: 10.059 s
>> [INFO] Finished at: 2018-04-05T09:14:17+01:00
>> [INFO]
>> ------------------------------------------------------------------------
>> [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar (attach-javadocs)
>> on project jena-base: Execution attach-javadocs of goal
>> org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar failed.:
>> NullPointerException -> [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 :jena-base
>>
>>
>> When I re-ran with mvn -e I got an NPE later in the build
>>
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Reactor Summary:
>> [INFO]
>> [INFO] Apache Jena 3.7.0 .................................. SUCCESS [
>> 1.264 s]
>> [INFO] Apache Jena - Shadowed external libraries .......... SUCCESS [
>> 1.607 s]
>> [INFO] Apache Jena - IRI .................................. SUCCESS [
>> 4.479 s]
>> [INFO] Apache Jena - Base Common Environment .............. SUCCESS [
>> 5.918 s]
>> [INFO] Apache Jena - Core ................................. SUCCESS [
>> 45.207 s]
>> [INFO] Apache Jena - ARQ (SPARQL 1.1 Query Engine) ........ SUCCESS [
>> 40.770 s]
>> [INFO] Apache Jena - RDF Connection ....................... SUCCESS [
>> 3.259 s]
>> [INFO] Apache Jena - TDB1 (Native Triple Store) ........... SUCCESS [
>> 24.833 s]
>> [INFO] Apache Jena - Database Operation Environment ....... SUCCESS [
>> 0.112 s]
>> [INFO] Apache Jena - DBOE Base ............................ SUCCESS [
>> 1.315 s]
>> [INFO] Apache Jena - DBOE Transactions .................... SUCCESS [
>> 0.988 s]
>> [INFO] Apache Jena - DBOE Indexes ......................... SUCCESS [
>> 0.203 s]
>> [INFO] Apache Jena - DBOE Index test suite ................ SUCCESS [
>> 0.217 s]
>> [INFO] Apache Jena - DBOE Transactional Datastructures .... SUCCESS [
>> 2.961 s]
>> [INFO] Apache Jena - TDB2 ................................. SUCCESS [
>> 11.631 s]
>> [INFO] Apache Jena - Libraries POM ........................ SUCCESS [
>> 0.159 s]
>> [INFO] Apache Jena - Command line tools ................... FAILURE [
>> 3.432 s]
>> [INFO] Apache Jena - SPARQL Text Search ................... SKIPPED
>> [INFO] Apache Jena - SPARQL Text Search - Elasticsearch ... SKIPPED
>> [INFO] Apache Jena - SPARQL Spatial Search ................ SKIPPED
>> [INFO] Apache Jena - Fuseki - A SPARQL 1.1 Server ......... SKIPPED
>> [INFO] Apache Jena - Fuseki Server Engine ................. SKIPPED
>> [INFO] Apache Jena - Fuseki Embedded Server ............... SKIPPED
>> [INFO] Apache Jena - Fuseki WAR File ...................... SKIPPED
>> [INFO] Apache Jena - Fuseki Server Standalone Jar ......... SKIPPED
>> [INFO] Apache Jena - Fuseki Basic Server .................. SKIPPED
>> [INFO] Apache Jena - Fuseki Binary Distribution ........... SKIPPED
>> [INFO] Apache Jena - Integration Testing .................. SKIPPED
>> [INFO] Apache Jena - Distribution ......................... SKIPPED
>> [INFO] Apache Jena - Fuseki1 .............................. SKIPPED
>> [INFO] Apache Jena - Data Tables for RDF and SPARQL ....... SKIPPED
>> [INFO] Apache Jena - SDB (SQL based triple store) ......... SKIPPED
>> [INFO] Apache Jena - Security Permissions ................. SKIPPED
>> [INFO] Apache Jena - Extras ............................... SKIPPED
>> [INFO] Apache Jena - Extras - Query Builder ............... SKIPPED
>> [INFO] Apache Jena - JDBC Parent .......................... SKIPPED
>> [INFO] Apache Jena - JDBC Core API ........................ SKIPPED
>> [INFO] Apache Jena - JDBC Remote Endpoint Driver .......... SKIPPED
>> [INFO] Apache Jena - JDBC In-Memory Driver ................ SKIPPED
>> [INFO] Apache Jena - JDBC TDB Driver ...................... SKIPPED
>> [INFO] Apache Jena - JDBC Driver Bundle ................... SKIPPED
>> [INFO] Apache Jena - Elephas .............................. SKIPPED
>> [INFO] Apache Jena - Elephas - Common API ................. SKIPPED
>> [INFO] Apache Jena - Elephas - I/O ........................ SKIPPED
>> [INFO] Apache Jena - Elephas - Map/Reduce ................. SKIPPED
>> [INFO] Apache Jena - Elephas - Statistics Demo App ........ SKIPPED
>> [INFO] Apache Jena - OSGi ................................. SKIPPED
>> [INFO] Apache Jena - OSGi bundle .......................... SKIPPED
>> [INFO] Apache Jena - OSGi Karaf features 3.7.0 ............ SKIPPED
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] BUILD FAILURE
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Total time: 02:29 min
>> [INFO] Finished at: 2018-04-05T09:18:46+01:00
>> [INFO]
>> ------------------------------------------------------------------------
>> [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar (attach-javadocs)
>> on project jena-cmds: Execution attach-javadocs of goal
>> org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar failed.:
>> NullPointerException -> [Help 1]
>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
>> goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar
>> (attach-javadocs) on project jena-cmds: Execution attach-javadocs of goal
>> org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar failed.
>>      at org.apache.maven.lifecycle.internal.MojoExecutor.execute
>> (MojoExecutor.java:213)
>>      at org.apache.maven.lifecycle.internal.MojoExecutor.execute
>> (MojoExecutor.java:154)
>>      at org.apache.maven.lifecycle.internal.MojoExecutor.execute
>> (MojoExecutor.java:146)
>>      at
>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
>> (LifecycleModuleBuilder.java:117)
>>      at
>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
>> (LifecycleModuleBuilder.java:81)
>>      at
>> org.apache.maven.lifecycle.internal.builder.singlethreaded.S
>> ingleThreadedBuilder.build
>> (SingleThreadedBuilder.java:56)
>>      at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
>> (LifecycleStarter.java:128)
>>      at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
>>      at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
>>      at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
>>      at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
>>      at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
>>      at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
>>      at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
>>      at sun.reflect.NativeMethodAccessorImpl.invoke
>> (NativeMethodAccessorImpl.java:62)
>>      at sun.reflect.DelegatingMethodAccessorImpl.invoke
>> (DelegatingMethodAccessorImpl.java:43)
>>      at java.lang.reflect.Method.invoke (Method.java:498)
>>      at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
>> (Launcher.java:289)
>>      at org.codehaus.plexus.classworlds.launcher.Launcher.launch
>> (Launcher.java:229)
>>      at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithEx
>> itCode
>> (Launcher.java:415)
>>      at org.codehaus.plexus.classworlds.launcher.Launcher.main
>> (Launcher.java:356)
>> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
>> attach-javadocs of goal
>> org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar failed.
>>      at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
>> (DefaultBuildPluginManager.java:148)
>>      at org.apache.maven.lifecycle.internal.MojoExecutor.execute
>> (MojoExecutor.java:208)
>>      at org.apache.maven.lifecycle.internal.MojoExecutor.execute
>> (MojoExecutor.java:154)
>>      at org.apache.maven.lifecycle.internal.MojoExecutor.execute
>> (MojoExecutor.java:146)
>>      at
>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
>> (LifecycleModuleBuilder.java:117)
>>      at
>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
>> (LifecycleModuleBuilder.java:81)
>>      at
>> org.apache.maven.lifecycle.internal.builder.singlethreaded.S
>> ingleThreadedBuilder.build
>> (SingleThreadedBuilder.java:56)
>>      at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
>> (LifecycleStarter.java:128)
>>      at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
>>      at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
>>      at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
>>      at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
>>      at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
>>      at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
>>      at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
>>      at sun.reflect.NativeMethodAccessorImpl.invoke (Nativ[INFO] ---
>> maven-javadoc-plugin:3.0.0:jar (attach-javadocs) @ jena-base ---
>> [INFO] The goal
>> 'org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:javadoc' has not
>> been
>> previously called for the module:
>> 'org.apache.jena:jena-shaded-guava:jar:3.7.0'. Trying to invoke it...
>> [WARNING] Creating fake javadoc directory to prevent repeated invocations:
>> /home/claude/git/jena/jena-shaded-guava/target/apidocs
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Reactor Summary:
>> [INFO]
>> [INFO] Apache Jena 3.7.0 .................................. SUCCESS [
>> 1.287 s]
>> [INFO] Apache Jena - Shadowed external libraries .......... SUCCESS [
>> 1.504 s]
>> [INFO] Apache Jena - IRI .................................. SUCCESS [
>> 2.575 s]
>> [INFO] Apache Jena - Base Common Environment .............. FAILURE [
>> 3.921 s]
>> [INFO] Apache Jena - Core ................................. SKIPPED
>> [INFO] Apache Jena - ARQ (SPARQL 1.1 Query Engine) ........ SKIPPED
>> [INFO] Apache Jena - RDF Connection ....................... SKIPPED
>> [INFO] Apache Jena - TDB1 (Native Triple Store) ........... SKIPPED
>> [INFO] Apache Jena - Database Operation Environment ....... SKIPPED
>> [INFO] Apache Jena - DBOE Base ............................ SKIPPED
>> [INFO] Apache Jena - DBOE Transactions .................... SKIPPED
>> [INFO] Apache Jena - DBOE Indexes ......................... SKIPPED
>> [INFO] Apache Jena - DBOE Index test suite ................ SKIPPED
>> [INFO] Apache Jena - DBOE Transactional Datastructures .... SKIPPED
>> [INFO] Apache Jena - TDB2 ................................. SKIPPED
>> [INFO] Apache Jena - Libraries POM ........................ SKIPPED
>> [INFO] Apache Jena - Command line tools ................... SKIPPED
>> [INFO] Apache Jena - SPARQL Text Search ................... SKIPPED
>> [INFO] Apache Jena - SPARQL Text Search - Elasticsearch ... SKIPPED
>> [INFO] Apache Jena - SPARQL Spatial Search ................ SKIPPED
>> [INFO] Apache Jena - Fuseki - A SPARQL 1.1 Server ......... SKIPPED
>> [INFO] Apache Jena - Fuseki Server Engine ................. SKIPPED
>> [INFO] Apache Jena - Fuseki Embedded Server ............... SKIPPED
>> [INFO] Apache Jena - Fuseki WAR File ...................... SKIPPED
>> [INFO] Apache Jena - Fuseki Server Standalone Jar ......... SKIPPED
>> [INFO] Apache Jena - Fuseki Basic Server .................. SKIPPED
>> [INFO] Apache Jena - Fuseki Binary Distribution ........... SKIPPED
>> [INFO] Apache Jena - Integration Testing .................. SKIPPED
>> [INFO] Apache Jena - Distribution ......................... SKIPPED
>> [INFO] Apache Jena - Fuseki1 .............................. SKIPPED
>> [INFO] Apache Jena - Data Tables for RDF and SPARQL ....... SKIPPED
>> [INFO] Apache Jena - SDB (SQL based triple store) ......... SKIPPED
>> [INFO] Apache Jena - Security Permissions ................. SKIPPED
>> [INFO] Apache Jena - Extras ............................... SKIPPED
>> [INFO] Apache Jena - Extras - Query Builder ............... SKIPPED
>> [INFO] Apache Jena - JDBC Parent .......................... SKIPPED
>> [INFO] Apache Jena - JDBC Core API ........................ SKIPPED
>> [INFO] Apache Jena - JDBC Remote Endpoint Driver .......... SKIPPED
>> [INFO] Apache Jena - JDBC In-Memory Driver ................ SKIPPED
>> [INFO] Apache Jena - JDBC TDB Driver ...................... SKIPPED
>> [INFO] Apache Jena - JDBC Driver Bundle ................... SKIPPED
>> [INFO] Apache Jena - Elephas .............................. SKIPPED
>> [INFO] Apache Jena - Elephas - Common API ................. SKIPPED
>> [INFO] Apache Jena - Elephas - I/O ........................ SKIPPED
>> [INFO] Apache Jena - Elephas - Map/Reduce ................. SKIPPED
>> [INFO] Apache Jena - Elephas - Statistics Demo App ........ SKIPPED
>> [INFO] Apache Jena - OSGi ................................. SKIPPED
>> [INFO] Apache Jena - OSGi bundle .......................... SKIPPED
>> [INFO] Apache Jena - OSGi Karaf features 3.7.0 ............ SKIPPED
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] BUILD FAILURE
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Total time: 10.059 s
>> [INFO] Finished at: 2018-04-05T09:14:17+01:00
>> [INFO]
>> ------------------------------------------------------------------------
>> [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar (attach-javadocs)
>> on project jena-base: Execution attach-javadocs of goal
>> org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar failed.:
>> NullPointerException -> [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 :jena-base
>> eMethodAccessorImpl.java:62)
>>      at sun.reflect.DelegatingMethodAccessorImpl.invoke
>> (DelegatingMethodAccessorImpl.java:43)
>>      at java.lang.reflect.Method.invoke (Method.java:498)
>>      at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
>> (Launcher.java:289)
>>      at org.codehaus.plexus.classworlds.launcher.Launcher.launch
>> (Launcher.java:229)
>>      at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithEx
>> itCode
>> (Launcher.java:415)
>>      at org.codehaus.plexus.classworlds.launcher.Launcher.main
>> (Launcher.java:356)
>> Caused by: java.lang.NullPointerException
>>      at java.io.File.<init> (File.java:277)
>>      at org.apache.maven.plugins.javadoc.JavadocUtil.getJavaHome
>> (JavadocUtil.java:1302)
>>      at org.apache.maven.plugins.javadoc.JavadocUtil.invokeMaven
>> (JavadocUtil.java:941)
>>      at org.apache.maven.plugins.javadoc.AbstractJavadocMojo.getModu
>> lesLinks
>> (AbstractJavadocMojo.java:5620)
>>      at
>> org.apache.maven.plugins.javadoc.AbstractJavadocMojo.addLink
>> offlineArguments
>> (AbstractJavadocMojo.java:4026)
>>      at
>> org.apache.maven.plugins.javadoc.AbstractJavadocMojo.addStan
>> dardDocletOptions
>> (AbstractJavadocMojo.java:4916)
>>      at org.apache.maven.plugins.javadoc.AbstractJavadocMojo.execute
>> Report
>> (AbstractJavadocMojo.java:2074)
>>      at org.apache.maven.plugins.javadoc.JavadocJar.doExecute
>> (JavadocJar.java:190)
>>      at org.apache.maven.plugins.javadoc.AbstractJavadocMojo.execute
>> (AbstractJavadocMojo.java:1909)
>>      at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
>> (DefaultBuildPluginManager.java:137)
>>      at org.apache.maven.lifecycle.internal.MojoExecutor.execute
>> (MojoExecutor.java:208)
>>      at org.apache.maven.lifecycle.internal.MojoExecutor.execute
>> (MojoExecutor.java:154)
>>      at org.apache.maven.lifecycle.internal.MojoExecutor.execute
>> (MojoExecutor.java:146)
>>      at
>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
>> (LifecycleModuleBuilder.java:117)
>>      at
>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
>> (LifecycleModuleBuilder.java:81)
>>      at
>> org.apache.maven.lifecycle.internal.builder.singlethreaded.S
>> ingleThreadedBuilder.build
>> (SingleThreadedBuilder.java:56)
>>      at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
>> (LifecycleStarter.java:128)
>>      at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
>>      at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
>>      at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
>>      at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
>>      at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
>>      at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
>>      at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
>>      at sun.reflect.NativeMethodAccessorImpl.invoke
>> (NativeMethodAccessorImpl.java:62)
>>      at sun.reflect.DelegatingMethodAccessorImpl.invoke
>> (DelegatingMethodAccessorImpl.java:43)
>>      at java.lang.reflect.Method.invoke (Method.java:498)
>>      at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
>> (Launcher.java:289)
>>      at org.codehaus.plexus.classworlds.launcher.Launcher.launch
>> (Launcher.java:229)
>>      at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithEx
>> itCode
>> (Launcher.java:415)
>>      at org.codehaus.plexus.classworlds.launcher.Launcher.main
>> (Launcher.java:356)
>> [ERROR]
>> [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 :jena-cmds
>>
>>
>> I think this only appears on a clean system with no previous build.  I am
>> doing this outside of an IDE and using Maven alone.
>>
>> claude@claude-XPS-15-9560:~/git/jena$ java -version
>> openjdk version "1.8.0_162"
>> OpenJDK Runtime Environment (build 1.8.0_162-8u162-b12-0ubuntu0.1
>> 6.04.2-b12)
>> OpenJDK 64-Bit Server VM (build 25.162-b12, mixed mode)
>> claude@claude-XPS-15-9560:~/git/jena$ mvn -version
>> Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297;
>> 2018-02-24T19:49:05Z)
>> Maven home: /usr/share/apache-maven-3.5.3
>> Java version: 1.8.0_162, vendor: Oracle Corporation
>> Java home: /usr/lib/jvm/java-8-openjdk-amd64/jre
>> Default locale: en_IE, platform encoding: UTF-8
>> OS name: "linux", version: "4.13.0-37-generic", arch: "amd64", family:
>> "unix"
>> claude@claude-XPS-15-9560:~/git/jena$ uname -a
>> Linux claude-XPS-15-9560 4.13.0-37-generic #42~16.04.1-Ubuntu SMP Wed Mar
>> 7
>> 16:03:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
>> claude@claude-XPS-15-9560:~/git/jena$
>>
>> Claude
>>
>> On Wed, Apr 4, 2018 at 4:17 PM, Andy Seaborne <an...@apache.org> wrote:
>>
>> There is a fix in PR#391.
>>>
>>> I've run the test case umpteen times now without incident and done
>>> performance times of bulkloading, which is about as write intensive as it
>>> gets.
>>>
>>> The worse slow down I observed (difference of a 3.6 and 3.7-fix) when
>>> loading 25M BSBM triples was 3%.  Usually it's 1%. Larger loads will be
>>> dominated by I/O costs so what is a CPU-related fix will be overtaken (I
>>> hope!). It did in the testing I did.
>>>
>>> So this email cancels RC1 and I'll start again.
>>>
>>>       Andy
>>>
>>>
>>> On 03/04/18 23:01, Andy Seaborne wrote:
>>>
>>> JENA-1516 looks serious and fixable.
>>>>
>>>> I'd like time to verify the fix that I have. As is often the case,
>>>> finding the concurrency problem is a lot more time consuming than
>>>> fixing an
>>>> identified problem.
>>>>
>>>> The WIP fix is available at
>>>>     https://github.com/afs/jena/tree/jena-1516_ObjectFileStorage
>>>> if you are really interested.
>>>>
>>>> If that fix looks good, I propose cancelling this RC and doing a new one
>>>> to include the fix.
>>>>
>>>> If the fix does not look good, and it has taken quite a heavy sustained
>>>> concurrent load to get anything to go wrong (carefully parallel 100
>>>> updates, 100 queries, 50 threads and it still does not happen every
>>>> time),
>>>> it seems better to continue RC1 and get a good fix done.
>>>>
>>>> Adam, Chris - thank you for the time to assess RC1.  There should be
>>>> very
>>>> little change between RC1 and a possible RC2.
>>>>
>>>> (not sure if SUSPENDED is a recognized state for a VOTE - think of it as
>>>> the RM needs time to do some more checking)
>>>>
>>>>       Andy
>>>>
>>>> On 29/03/18 19:28, Andy Seaborne wrote:
>>>>
>>>> Hi,
>>>>>
>>>>> Here is a vote on a release of Jena 3.7.0.
>>>>>
>>>>> This is the first proposed candidate for a 3.7.0 release.
>>>>>
>>>>> There are process changes.
>>>>>
>>>>> Deadline:
>>>>>
>>>>>          2018-04-01 22:00 UTC
>>>>>
>>>>> April 1st!
>>>>>
>>>>> ==== Process Changes
>>>>>
>>>>> 1/
>>>>> MD5 files are being discouraged because MD5 is not secure.  Projects
>>>>> are
>>>>> now asked to not publish md5.
>>>>>
>>>>> There are no md5 files in the proposed dist/jena area - files on Apache
>>>>> hardware.
>>>>>
>>>>> There are sha1 and sha512 checksums.
>>>>> * The sha512 is in Linux sha512sum checkable format.
>>>>> * The sha1 is whatever maven generated and is the same as will go to
>>>>> maven central.
>>>>>
>>>>> Having the sha1 ties the dist/jena artifacts to maven central (as does
>>>>> the .asc).
>>>>>
>>>>> There are md5 and sha1 in the proposes maven repo staging area for
>>>>> sending to maven central. That part of maven is hardwired to md5/sha1
>>>>> still.
>>>>>
>>>>> There's a script to setup the sha512.
>>>>>
>>>>> 2/
>>>>> To establish the proof chain for signed artifacts in /dist/project/, I
>>>>> have been asked to try out the new META files.
>>>>>
>>>>> https://checker.apache.org/doc/README.html#ch-meta
>>>>>
>>>>> There are two files
>>>>>
>>>>> /dist/jena/META
>>>>> /dist/jena/META.asc
>>>>>
>>>>> META says who signs what, and is itself signed by the PMC chair.
>>>>>
>>>>> ==== Release changes
>>>>>
>>>>> 55 JIRA:
>>>>> https://s.apache.org/jena-3.7.0-jira
>>>>>
>>>>> == Significant Changes
>>>>>
>>>>> ** Java9: Building and running on a Java9 platform is supported
>>>>>
>>>>> JENA-1461 - Allow ARQ custom functions to be written in JavaScript
>>>>>
>>>>> JENA-1389 - Return `this` rather than `void` from Dataset (API change)
>>>>> JENA-1495 - Return Model from PrefixMapping methods (API change)
>>>>>
>>>>> JENA-1458, JENA-1483 - Transaction Promotion
>>>>>
>>>>> JENA-1453 - Lucene indexes using a graph field are smaller
>>>>>
>>>>> JENA-1490 - Working with Blank Nodes with Fuseki
>>>>>
>>>>> == Upgrades to libraries (runtime dependencies):
>>>>>
>>>>> No dependency changes.
>>>>>
>>>>> ==== Release Vote
>>>>>
>>>>> Everyone, not just committers, is invited to test and vote.
>>>>> Please download and test the proposed release.
>>>>>
>>>>> Proposed dist/ area:
>>>>>     https://dist.apache.org/repos/dist/dev/jena/
>>>>>
>>>>> Keys:
>>>>>     https://svn.apache.org/repos/asf/jena/dist/KEYS
>>>>>
>>>>> Staging repository:
>>>>>     https://repository.apache.org/content/repositories/orgapache
>>>>> jena-1022/
>>>>>
>>>>> Git commit (browser URL):
>>>>> https://git1-us-west.apache.org/repos/asf?p=jena.git;a=commi
>>>>> t;h=d4e7063e
>>>>>
>>>>> Git Commit Hash:
>>>>>     d4e7063e7a6db8ce77699bd0388e1a1bd6816626
>>>>>
>>>>> Git Commit Tag:
>>>>>        jena-3.7.0-rc1
>>>>>
>>>>> Please vote to approve this release:
>>>>>
>>>>>          [ ] +1 Approve the release
>>>>>          [ ]  0 Don't care
>>>>>          [ ] -1 Don't release, because ...
>>>>>
>>>>> This vote will be open until at least
>>>>>
>>>>>          2018-04-01 22:00 UTC
>>>>>
>>>>> If you expect to check the release but the time 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?
>>>>>
>>>>>
>>>>
>>
>>


-- 
I like: Like Like - The likeliest place on the web
<http://like-like.xenei.com>
LinkedIn: http://www.linkedin.com/in/claudewarren

Re: [] Apache Jena 3.7.0 RC1

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

I grabbed the latest version of maven so as to run with exactly the same 
version of maven. Building current development (reset to 3.7.0-SNAPSHOT) 
worked for me.

The javadoc doc for 3.7.0 is already loaded onto jena.staging.

We now have 4 (if you include jenkins) independent reports of success.

It must be quite frustrating but if there is a non-deterministic bug in 
the javadoc:attach-javadocs goal, there is not a lot we can do.

The update to plugin-javadoc:3.0.0 was necessary to run with a Java9 JDK 
but you could try locally running with an earlier one.  (Or skip javadoc 
because it is on the web and can be downloaded in javadoc jars.)

There is some recent stackoverflow foo that looks like it but it seems 
to be Java10 related.

     Andy

On 05/04/18 09:26, Claude Warren wrote:
> Following up on the NPE I reported.  I switched to the original RC1 code
> and had the same issue.
> 
> Intiial run reported:
> [INFO] --- maven-javadoc-plugin:3.0.0:jar (attach-javadocs) @ jena-base ---
> [INFO] The goal
> 'org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:javadoc' has not been
> previously called for the module:
> 'org.apache.jena:jena-shaded-guava:jar:3.7.0'. Trying to invoke it...
> [WARNING] Creating fake javadoc directory to prevent repeated invocations:
> /home/claude/git/jena/jena-shaded-guava/target/apidocs
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache Jena 3.7.0 .................................. SUCCESS [
> 1.287 s]
> [INFO] Apache Jena - Shadowed external libraries .......... SUCCESS [
> 1.504 s]
> [INFO] Apache Jena - IRI .................................. SUCCESS [
> 2.575 s]
> [INFO] Apache Jena - Base Common Environment .............. FAILURE [
> 3.921 s]
> [INFO] Apache Jena - Core ................................. SKIPPED
> [INFO] Apache Jena - ARQ (SPARQL 1.1 Query Engine) ........ SKIPPED
> [INFO] Apache Jena - RDF Connection ....................... SKIPPED
> [INFO] Apache Jena - TDB1 (Native Triple Store) ........... SKIPPED
> [INFO] Apache Jena - Database Operation Environment ....... SKIPPED
> [INFO] Apache Jena - DBOE Base ............................ SKIPPED
> [INFO] Apache Jena - DBOE Transactions .................... SKIPPED
> [INFO] Apache Jena - DBOE Indexes ......................... SKIPPED
> [INFO] Apache Jena - DBOE Index test suite ................ SKIPPED
> [INFO] Apache Jena - DBOE Transactional Datastructures .... SKIPPED
> [INFO] Apache Jena - TDB2 ................................. SKIPPED
> [INFO] Apache Jena - Libraries POM ........................ SKIPPED
> [INFO] Apache Jena - Command line tools ................... SKIPPED
> [INFO] Apache Jena - SPARQL Text Search ................... SKIPPED
> [INFO] Apache Jena - SPARQL Text Search - Elasticsearch ... SKIPPED
> [INFO] Apache Jena - SPARQL Spatial Search ................ SKIPPED
> [INFO] Apache Jena - Fuseki - A SPARQL 1.1 Server ......... SKIPPED
> [INFO] Apache Jena - Fuseki Server Engine ................. SKIPPED
> [INFO] Apache Jena - Fuseki Embedded Server ............... SKIPPED
> [INFO] Apache Jena - Fuseki WAR File ...................... SKIPPED
> [INFO] Apache Jena - Fuseki Server Standalone Jar ......... SKIPPED
> [INFO] Apache Jena - Fuseki Basic Server .................. SKIPPED
> [INFO] Apache Jena - Fuseki Binary Distribution ........... SKIPPED
> [INFO] Apache Jena - Integration Testing .................. SKIPPED
> [INFO] Apache Jena - Distribution ......................... SKIPPED
> [INFO] Apache Jena - Fuseki1 .............................. SKIPPED
> [INFO] Apache Jena - Data Tables for RDF and SPARQL ....... SKIPPED
> [INFO] Apache Jena - SDB (SQL based triple store) ......... SKIPPED
> [INFO] Apache Jena - Security Permissions ................. SKIPPED
> [INFO] Apache Jena - Extras ............................... SKIPPED
> [INFO] Apache Jena - Extras - Query Builder ............... SKIPPED
> [INFO] Apache Jena - JDBC Parent .......................... SKIPPED
> [INFO] Apache Jena - JDBC Core API ........................ SKIPPED
> [INFO] Apache Jena - JDBC Remote Endpoint Driver .......... SKIPPED
> [INFO] Apache Jena - JDBC In-Memory Driver ................ SKIPPED
> [INFO] Apache Jena - JDBC TDB Driver ...................... SKIPPED
> [INFO] Apache Jena - JDBC Driver Bundle ................... SKIPPED
> [INFO] Apache Jena - Elephas .............................. SKIPPED
> [INFO] Apache Jena - Elephas - Common API ................. SKIPPED
> [INFO] Apache Jena - Elephas - I/O ........................ SKIPPED
> [INFO] Apache Jena - Elephas - Map/Reduce ................. SKIPPED
> [INFO] Apache Jena - Elephas - Statistics Demo App ........ SKIPPED
> [INFO] Apache Jena - OSGi ................................. SKIPPED
> [INFO] Apache Jena - OSGi bundle .......................... SKIPPED
> [INFO] Apache Jena - OSGi Karaf features 3.7.0 ............ SKIPPED
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 10.059 s
> [INFO] Finished at: 2018-04-05T09:14:17+01:00
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar (attach-javadocs)
> on project jena-base: Execution attach-javadocs of goal
> org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar failed.:
> NullPointerException -> [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 :jena-base
> 
> 
> When I re-ran with mvn -e I got an NPE later in the build
> 
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache Jena 3.7.0 .................................. SUCCESS [
> 1.264 s]
> [INFO] Apache Jena - Shadowed external libraries .......... SUCCESS [
> 1.607 s]
> [INFO] Apache Jena - IRI .................................. SUCCESS [
> 4.479 s]
> [INFO] Apache Jena - Base Common Environment .............. SUCCESS [
> 5.918 s]
> [INFO] Apache Jena - Core ................................. SUCCESS [
> 45.207 s]
> [INFO] Apache Jena - ARQ (SPARQL 1.1 Query Engine) ........ SUCCESS [
> 40.770 s]
> [INFO] Apache Jena - RDF Connection ....................... SUCCESS [
> 3.259 s]
> [INFO] Apache Jena - TDB1 (Native Triple Store) ........... SUCCESS [
> 24.833 s]
> [INFO] Apache Jena - Database Operation Environment ....... SUCCESS [
> 0.112 s]
> [INFO] Apache Jena - DBOE Base ............................ SUCCESS [
> 1.315 s]
> [INFO] Apache Jena - DBOE Transactions .................... SUCCESS [
> 0.988 s]
> [INFO] Apache Jena - DBOE Indexes ......................... SUCCESS [
> 0.203 s]
> [INFO] Apache Jena - DBOE Index test suite ................ SUCCESS [
> 0.217 s]
> [INFO] Apache Jena - DBOE Transactional Datastructures .... SUCCESS [
> 2.961 s]
> [INFO] Apache Jena - TDB2 ................................. SUCCESS [
> 11.631 s]
> [INFO] Apache Jena - Libraries POM ........................ SUCCESS [
> 0.159 s]
> [INFO] Apache Jena - Command line tools ................... FAILURE [
> 3.432 s]
> [INFO] Apache Jena - SPARQL Text Search ................... SKIPPED
> [INFO] Apache Jena - SPARQL Text Search - Elasticsearch ... SKIPPED
> [INFO] Apache Jena - SPARQL Spatial Search ................ SKIPPED
> [INFO] Apache Jena - Fuseki - A SPARQL 1.1 Server ......... SKIPPED
> [INFO] Apache Jena - Fuseki Server Engine ................. SKIPPED
> [INFO] Apache Jena - Fuseki Embedded Server ............... SKIPPED
> [INFO] Apache Jena - Fuseki WAR File ...................... SKIPPED
> [INFO] Apache Jena - Fuseki Server Standalone Jar ......... SKIPPED
> [INFO] Apache Jena - Fuseki Basic Server .................. SKIPPED
> [INFO] Apache Jena - Fuseki Binary Distribution ........... SKIPPED
> [INFO] Apache Jena - Integration Testing .................. SKIPPED
> [INFO] Apache Jena - Distribution ......................... SKIPPED
> [INFO] Apache Jena - Fuseki1 .............................. SKIPPED
> [INFO] Apache Jena - Data Tables for RDF and SPARQL ....... SKIPPED
> [INFO] Apache Jena - SDB (SQL based triple store) ......... SKIPPED
> [INFO] Apache Jena - Security Permissions ................. SKIPPED
> [INFO] Apache Jena - Extras ............................... SKIPPED
> [INFO] Apache Jena - Extras - Query Builder ............... SKIPPED
> [INFO] Apache Jena - JDBC Parent .......................... SKIPPED
> [INFO] Apache Jena - JDBC Core API ........................ SKIPPED
> [INFO] Apache Jena - JDBC Remote Endpoint Driver .......... SKIPPED
> [INFO] Apache Jena - JDBC In-Memory Driver ................ SKIPPED
> [INFO] Apache Jena - JDBC TDB Driver ...................... SKIPPED
> [INFO] Apache Jena - JDBC Driver Bundle ................... SKIPPED
> [INFO] Apache Jena - Elephas .............................. SKIPPED
> [INFO] Apache Jena - Elephas - Common API ................. SKIPPED
> [INFO] Apache Jena - Elephas - I/O ........................ SKIPPED
> [INFO] Apache Jena - Elephas - Map/Reduce ................. SKIPPED
> [INFO] Apache Jena - Elephas - Statistics Demo App ........ SKIPPED
> [INFO] Apache Jena - OSGi ................................. SKIPPED
> [INFO] Apache Jena - OSGi bundle .......................... SKIPPED
> [INFO] Apache Jena - OSGi Karaf features 3.7.0 ............ SKIPPED
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 02:29 min
> [INFO] Finished at: 2018-04-05T09:18:46+01:00
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar (attach-javadocs)
> on project jena-cmds: Execution attach-javadocs of goal
> org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar failed.:
> NullPointerException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar
> (attach-javadocs) on project jena-cmds: Execution attach-javadocs of goal
> org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar failed.
>      at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:213)
>      at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:154)
>      at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:146)
>      at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
>      at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
>      at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:56)
>      at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
>      at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
>      at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
>      at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
>      at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
>      at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
>      at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
>      at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
>      at sun.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
>      at sun.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
>      at java.lang.reflect.Method.invoke (Method.java:498)
>      at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:289)
>      at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:229)
>      at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:415)
>      at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:356)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
> attach-javadocs of goal
> org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar failed.
>      at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:148)
>      at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:208)
>      at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:154)
>      at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:146)
>      at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
>      at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
>      at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:56)
>      at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
>      at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
>      at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
>      at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
>      at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
>      at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
>      at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
>      at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
>      at sun.reflect.NativeMethodAccessorImpl.invoke (Nativ[INFO] ---
> maven-javadoc-plugin:3.0.0:jar (attach-javadocs) @ jena-base ---
> [INFO] The goal
> 'org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:javadoc' has not been
> previously called for the module:
> 'org.apache.jena:jena-shaded-guava:jar:3.7.0'. Trying to invoke it...
> [WARNING] Creating fake javadoc directory to prevent repeated invocations:
> /home/claude/git/jena/jena-shaded-guava/target/apidocs
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache Jena 3.7.0 .................................. SUCCESS [
> 1.287 s]
> [INFO] Apache Jena - Shadowed external libraries .......... SUCCESS [
> 1.504 s]
> [INFO] Apache Jena - IRI .................................. SUCCESS [
> 2.575 s]
> [INFO] Apache Jena - Base Common Environment .............. FAILURE [
> 3.921 s]
> [INFO] Apache Jena - Core ................................. SKIPPED
> [INFO] Apache Jena - ARQ (SPARQL 1.1 Query Engine) ........ SKIPPED
> [INFO] Apache Jena - RDF Connection ....................... SKIPPED
> [INFO] Apache Jena - TDB1 (Native Triple Store) ........... SKIPPED
> [INFO] Apache Jena - Database Operation Environment ....... SKIPPED
> [INFO] Apache Jena - DBOE Base ............................ SKIPPED
> [INFO] Apache Jena - DBOE Transactions .................... SKIPPED
> [INFO] Apache Jena - DBOE Indexes ......................... SKIPPED
> [INFO] Apache Jena - DBOE Index test suite ................ SKIPPED
> [INFO] Apache Jena - DBOE Transactional Datastructures .... SKIPPED
> [INFO] Apache Jena - TDB2 ................................. SKIPPED
> [INFO] Apache Jena - Libraries POM ........................ SKIPPED
> [INFO] Apache Jena - Command line tools ................... SKIPPED
> [INFO] Apache Jena - SPARQL Text Search ................... SKIPPED
> [INFO] Apache Jena - SPARQL Text Search - Elasticsearch ... SKIPPED
> [INFO] Apache Jena - SPARQL Spatial Search ................ SKIPPED
> [INFO] Apache Jena - Fuseki - A SPARQL 1.1 Server ......... SKIPPED
> [INFO] Apache Jena - Fuseki Server Engine ................. SKIPPED
> [INFO] Apache Jena - Fuseki Embedded Server ............... SKIPPED
> [INFO] Apache Jena - Fuseki WAR File ...................... SKIPPED
> [INFO] Apache Jena - Fuseki Server Standalone Jar ......... SKIPPED
> [INFO] Apache Jena - Fuseki Basic Server .................. SKIPPED
> [INFO] Apache Jena - Fuseki Binary Distribution ........... SKIPPED
> [INFO] Apache Jena - Integration Testing .................. SKIPPED
> [INFO] Apache Jena - Distribution ......................... SKIPPED
> [INFO] Apache Jena - Fuseki1 .............................. SKIPPED
> [INFO] Apache Jena - Data Tables for RDF and SPARQL ....... SKIPPED
> [INFO] Apache Jena - SDB (SQL based triple store) ......... SKIPPED
> [INFO] Apache Jena - Security Permissions ................. SKIPPED
> [INFO] Apache Jena - Extras ............................... SKIPPED
> [INFO] Apache Jena - Extras - Query Builder ............... SKIPPED
> [INFO] Apache Jena - JDBC Parent .......................... SKIPPED
> [INFO] Apache Jena - JDBC Core API ........................ SKIPPED
> [INFO] Apache Jena - JDBC Remote Endpoint Driver .......... SKIPPED
> [INFO] Apache Jena - JDBC In-Memory Driver ................ SKIPPED
> [INFO] Apache Jena - JDBC TDB Driver ...................... SKIPPED
> [INFO] Apache Jena - JDBC Driver Bundle ................... SKIPPED
> [INFO] Apache Jena - Elephas .............................. SKIPPED
> [INFO] Apache Jena - Elephas - Common API ................. SKIPPED
> [INFO] Apache Jena - Elephas - I/O ........................ SKIPPED
> [INFO] Apache Jena - Elephas - Map/Reduce ................. SKIPPED
> [INFO] Apache Jena - Elephas - Statistics Demo App ........ SKIPPED
> [INFO] Apache Jena - OSGi ................................. SKIPPED
> [INFO] Apache Jena - OSGi bundle .......................... SKIPPED
> [INFO] Apache Jena - OSGi Karaf features 3.7.0 ............ SKIPPED
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 10.059 s
> [INFO] Finished at: 2018-04-05T09:14:17+01:00
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar (attach-javadocs)
> on project jena-base: Execution attach-javadocs of goal
> org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar failed.:
> NullPointerException -> [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 :jena-base
> eMethodAccessorImpl.java:62)
>      at sun.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
>      at java.lang.reflect.Method.invoke (Method.java:498)
>      at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:289)
>      at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:229)
>      at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:415)
>      at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:356)
> Caused by: java.lang.NullPointerException
>      at java.io.File.<init> (File.java:277)
>      at org.apache.maven.plugins.javadoc.JavadocUtil.getJavaHome
> (JavadocUtil.java:1302)
>      at org.apache.maven.plugins.javadoc.JavadocUtil.invokeMaven
> (JavadocUtil.java:941)
>      at org.apache.maven.plugins.javadoc.AbstractJavadocMojo.getModulesLinks
> (AbstractJavadocMojo.java:5620)
>      at
> org.apache.maven.plugins.javadoc.AbstractJavadocMojo.addLinkofflineArguments
> (AbstractJavadocMojo.java:4026)
>      at
> org.apache.maven.plugins.javadoc.AbstractJavadocMojo.addStandardDocletOptions
> (AbstractJavadocMojo.java:4916)
>      at org.apache.maven.plugins.javadoc.AbstractJavadocMojo.executeReport
> (AbstractJavadocMojo.java:2074)
>      at org.apache.maven.plugins.javadoc.JavadocJar.doExecute
> (JavadocJar.java:190)
>      at org.apache.maven.plugins.javadoc.AbstractJavadocMojo.execute
> (AbstractJavadocMojo.java:1909)
>      at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:137)
>      at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:208)
>      at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:154)
>      at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:146)
>      at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
>      at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
>      at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:56)
>      at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
>      at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
>      at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
>      at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
>      at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
>      at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
>      at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
>      at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
>      at sun.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
>      at sun.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
>      at java.lang.reflect.Method.invoke (Method.java:498)
>      at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:289)
>      at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:229)
>      at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:415)
>      at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:356)
> [ERROR]
> [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 :jena-cmds
> 
> 
> I think this only appears on a clean system with no previous build.  I am
> doing this outside of an IDE and using Maven alone.
> 
> claude@claude-XPS-15-9560:~/git/jena$ java -version
> openjdk version "1.8.0_162"
> OpenJDK Runtime Environment (build 1.8.0_162-8u162-b12-0ubuntu0.16.04.2-b12)
> OpenJDK 64-Bit Server VM (build 25.162-b12, mixed mode)
> claude@claude-XPS-15-9560:~/git/jena$ mvn -version
> Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297;
> 2018-02-24T19:49:05Z)
> Maven home: /usr/share/apache-maven-3.5.3
> Java version: 1.8.0_162, vendor: Oracle Corporation
> Java home: /usr/lib/jvm/java-8-openjdk-amd64/jre
> Default locale: en_IE, platform encoding: UTF-8
> OS name: "linux", version: "4.13.0-37-generic", arch: "amd64", family:
> "unix"
> claude@claude-XPS-15-9560:~/git/jena$ uname -a
> Linux claude-XPS-15-9560 4.13.0-37-generic #42~16.04.1-Ubuntu SMP Wed Mar 7
> 16:03:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
> claude@claude-XPS-15-9560:~/git/jena$
> 
> Claude
> 
> On Wed, Apr 4, 2018 at 4:17 PM, Andy Seaborne <an...@apache.org> wrote:
> 
>> There is a fix in PR#391.
>>
>> I've run the test case umpteen times now without incident and done
>> performance times of bulkloading, which is about as write intensive as it
>> gets.
>>
>> The worse slow down I observed (difference of a 3.6 and 3.7-fix) when
>> loading 25M BSBM triples was 3%.  Usually it's 1%. Larger loads will be
>> dominated by I/O costs so what is a CPU-related fix will be overtaken (I
>> hope!). It did in the testing I did.
>>
>> So this email cancels RC1 and I'll start again.
>>
>>       Andy
>>
>>
>> On 03/04/18 23:01, Andy Seaborne wrote:
>>
>>> JENA-1516 looks serious and fixable.
>>>
>>> I'd like time to verify the fix that I have. As is often the case,
>>> finding the concurrency problem is a lot more time consuming than fixing an
>>> identified problem.
>>>
>>> The WIP fix is available at
>>>     https://github.com/afs/jena/tree/jena-1516_ObjectFileStorage
>>> if you are really interested.
>>>
>>> If that fix looks good, I propose cancelling this RC and doing a new one
>>> to include the fix.
>>>
>>> If the fix does not look good, and it has taken quite a heavy sustained
>>> concurrent load to get anything to go wrong (carefully parallel 100
>>> updates, 100 queries, 50 threads and it still does not happen every time),
>>> it seems better to continue RC1 and get a good fix done.
>>>
>>> Adam, Chris - thank you for the time to assess RC1.  There should be very
>>> little change between RC1 and a possible RC2.
>>>
>>> (not sure if SUSPENDED is a recognized state for a VOTE - think of it as
>>> the RM needs time to do some more checking)
>>>
>>>       Andy
>>>
>>> On 29/03/18 19:28, Andy Seaborne wrote:
>>>
>>>> Hi,
>>>>
>>>> Here is a vote on a release of Jena 3.7.0.
>>>>
>>>> This is the first proposed candidate for a 3.7.0 release.
>>>>
>>>> There are process changes.
>>>>
>>>> Deadline:
>>>>
>>>>          2018-04-01 22:00 UTC
>>>>
>>>> April 1st!
>>>>
>>>> ==== Process Changes
>>>>
>>>> 1/
>>>> MD5 files are being discouraged because MD5 is not secure.  Projects are
>>>> now asked to not publish md5.
>>>>
>>>> There are no md5 files in the proposed dist/jena area - files on Apache
>>>> hardware.
>>>>
>>>> There are sha1 and sha512 checksums.
>>>> * The sha512 is in Linux sha512sum checkable format.
>>>> * The sha1 is whatever maven generated and is the same as will go to
>>>> maven central.
>>>>
>>>> Having the sha1 ties the dist/jena artifacts to maven central (as does
>>>> the .asc).
>>>>
>>>> There are md5 and sha1 in the proposes maven repo staging area for
>>>> sending to maven central. That part of maven is hardwired to md5/sha1 still.
>>>>
>>>> There's a script to setup the sha512.
>>>>
>>>> 2/
>>>> To establish the proof chain for signed artifacts in /dist/project/, I
>>>> have been asked to try out the new META files.
>>>>
>>>> https://checker.apache.org/doc/README.html#ch-meta
>>>>
>>>> There are two files
>>>>
>>>> /dist/jena/META
>>>> /dist/jena/META.asc
>>>>
>>>> META says who signs what, and is itself signed by the PMC chair.
>>>>
>>>> ==== Release changes
>>>>
>>>> 55 JIRA:
>>>> https://s.apache.org/jena-3.7.0-jira
>>>>
>>>> == Significant Changes
>>>>
>>>> ** Java9: Building and running on a Java9 platform is supported
>>>>
>>>> JENA-1461 - Allow ARQ custom functions to be written in JavaScript
>>>>
>>>> JENA-1389 - Return `this` rather than `void` from Dataset (API change)
>>>> JENA-1495 - Return Model from PrefixMapping methods (API change)
>>>>
>>>> JENA-1458, JENA-1483 - Transaction Promotion
>>>>
>>>> JENA-1453 - Lucene indexes using a graph field are smaller
>>>>
>>>> JENA-1490 - Working with Blank Nodes with Fuseki
>>>>
>>>> == Upgrades to libraries (runtime dependencies):
>>>>
>>>> No dependency changes.
>>>>
>>>> ==== Release Vote
>>>>
>>>> Everyone, not just committers, is invited to test and vote.
>>>> Please download and test the proposed release.
>>>>
>>>> Proposed dist/ area:
>>>>     https://dist.apache.org/repos/dist/dev/jena/
>>>>
>>>> Keys:
>>>>     https://svn.apache.org/repos/asf/jena/dist/KEYS
>>>>
>>>> Staging repository:
>>>>     https://repository.apache.org/content/repositories/orgapache
>>>> jena-1022/
>>>>
>>>> Git commit (browser URL):
>>>> https://git1-us-west.apache.org/repos/asf?p=jena.git;a=commit;h=d4e7063e
>>>>
>>>> Git Commit Hash:
>>>>     d4e7063e7a6db8ce77699bd0388e1a1bd6816626
>>>>
>>>> Git Commit Tag:
>>>>        jena-3.7.0-rc1
>>>>
>>>> Please vote to approve this release:
>>>>
>>>>          [ ] +1 Approve the release
>>>>          [ ]  0 Don't care
>>>>          [ ] -1 Don't release, because ...
>>>>
>>>> This vote will be open until at least
>>>>
>>>>          2018-04-01 22:00 UTC
>>>>
>>>> If you expect to check the release but the time 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: [CANCELLED] Apache Jena 3.7.0 RC1

Posted by Claude Warren <cl...@xenei.com>.

Following up on the NPE I reported.  I switched to the original RC1 code
and had the same issue.

Intiial run reported:
[INFO] --- maven-javadoc-plugin:3.0.0:jar (attach-javadocs) @ jena-base ---
[INFO] The goal
'org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:javadoc' has not been
previously called for the module:
'org.apache.jena:jena-shaded-guava:jar:3.7.0'. Trying to invoke it...
[WARNING] Creating fake javadoc directory to prevent repeated invocations:
/home/claude/git/jena/jena-shaded-guava/target/apidocs
[INFO]
------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Jena 3.7.0 .................................. SUCCESS [
1.287 s]
[INFO] Apache Jena - Shadowed external libraries .......... SUCCESS [
1.504 s]
[INFO] Apache Jena - IRI .................................. SUCCESS [
2.575 s]
[INFO] Apache Jena - Base Common Environment .............. FAILURE [
3.921 s]
[INFO] Apache Jena - Core ................................. SKIPPED
[INFO] Apache Jena - ARQ (SPARQL 1.1 Query Engine) ........ SKIPPED
[INFO] Apache Jena - RDF Connection ....................... SKIPPED
[INFO] Apache Jena - TDB1 (Native Triple Store) ........... SKIPPED
[INFO] Apache Jena - Database Operation Environment ....... SKIPPED
[INFO] Apache Jena - DBOE Base ............................ SKIPPED
[INFO] Apache Jena - DBOE Transactions .................... SKIPPED
[INFO] Apache Jena - DBOE Indexes ......................... SKIPPED
[INFO] Apache Jena - DBOE Index test suite ................ SKIPPED
[INFO] Apache Jena - DBOE Transactional Datastructures .... SKIPPED
[INFO] Apache Jena - TDB2 ................................. SKIPPED
[INFO] Apache Jena - Libraries POM ........................ SKIPPED
[INFO] Apache Jena - Command line tools ................... SKIPPED
[INFO] Apache Jena - SPARQL Text Search ................... SKIPPED
[INFO] Apache Jena - SPARQL Text Search - Elasticsearch ... SKIPPED
[INFO] Apache Jena - SPARQL Spatial Search ................ SKIPPED
[INFO] Apache Jena - Fuseki - A SPARQL 1.1 Server ......... SKIPPED
[INFO] Apache Jena - Fuseki Server Engine ................. SKIPPED
[INFO] Apache Jena - Fuseki Embedded Server ............... SKIPPED
[INFO] Apache Jena - Fuseki WAR File ...................... SKIPPED
[INFO] Apache Jena - Fuseki Server Standalone Jar ......... SKIPPED
[INFO] Apache Jena - Fuseki Basic Server .................. SKIPPED
[INFO] Apache Jena - Fuseki Binary Distribution ........... SKIPPED
[INFO] Apache Jena - Integration Testing .................. SKIPPED
[INFO] Apache Jena - Distribution ......................... SKIPPED
[INFO] Apache Jena - Fuseki1 .............................. SKIPPED
[INFO] Apache Jena - Data Tables for RDF and SPARQL ....... SKIPPED
[INFO] Apache Jena - SDB (SQL based triple store) ......... SKIPPED
[INFO] Apache Jena - Security Permissions ................. SKIPPED
[INFO] Apache Jena - Extras ............................... SKIPPED
[INFO] Apache Jena - Extras - Query Builder ............... SKIPPED
[INFO] Apache Jena - JDBC Parent .......................... SKIPPED
[INFO] Apache Jena - JDBC Core API ........................ SKIPPED
[INFO] Apache Jena - JDBC Remote Endpoint Driver .......... SKIPPED
[INFO] Apache Jena - JDBC In-Memory Driver ................ SKIPPED
[INFO] Apache Jena - JDBC TDB Driver ...................... SKIPPED
[INFO] Apache Jena - JDBC Driver Bundle ................... SKIPPED
[INFO] Apache Jena - Elephas .............................. SKIPPED
[INFO] Apache Jena - Elephas - Common API ................. SKIPPED
[INFO] Apache Jena - Elephas - I/O ........................ SKIPPED
[INFO] Apache Jena - Elephas - Map/Reduce ................. SKIPPED
[INFO] Apache Jena - Elephas - Statistics Demo App ........ SKIPPED
[INFO] Apache Jena - OSGi ................................. SKIPPED
[INFO] Apache Jena - OSGi bundle .......................... SKIPPED
[INFO] Apache Jena - OSGi Karaf features 3.7.0 ............ SKIPPED
[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 10.059 s
[INFO] Finished at: 2018-04-05T09:14:17+01:00
[INFO]
------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar (attach-javadocs)
on project jena-base: Execution attach-javadocs of goal
org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar failed.:
NullPointerException -> [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 :jena-base


When I re-ran with mvn -e I got an NPE later in the build

[INFO]
------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Jena 3.7.0 .................................. SUCCESS [
1.264 s]
[INFO] Apache Jena - Shadowed external libraries .......... SUCCESS [
1.607 s]
[INFO] Apache Jena - IRI .................................. SUCCESS [
4.479 s]
[INFO] Apache Jena - Base Common Environment .............. SUCCESS [
5.918 s]
[INFO] Apache Jena - Core ................................. SUCCESS [
45.207 s]
[INFO] Apache Jena - ARQ (SPARQL 1.1 Query Engine) ........ SUCCESS [
40.770 s]
[INFO] Apache Jena - RDF Connection ....................... SUCCESS [
3.259 s]
[INFO] Apache Jena - TDB1 (Native Triple Store) ........... SUCCESS [
24.833 s]
[INFO] Apache Jena - Database Operation Environment ....... SUCCESS [
0.112 s]
[INFO] Apache Jena - DBOE Base ............................ SUCCESS [
1.315 s]
[INFO] Apache Jena - DBOE Transactions .................... SUCCESS [
0.988 s]
[INFO] Apache Jena - DBOE Indexes ......................... SUCCESS [
0.203 s]
[INFO] Apache Jena - DBOE Index test suite ................ SUCCESS [
0.217 s]
[INFO] Apache Jena - DBOE Transactional Datastructures .... SUCCESS [
2.961 s]
[INFO] Apache Jena - TDB2 ................................. SUCCESS [
11.631 s]
[INFO] Apache Jena - Libraries POM ........................ SUCCESS [
0.159 s]
[INFO] Apache Jena - Command line tools ................... FAILURE [
3.432 s]
[INFO] Apache Jena - SPARQL Text Search ................... SKIPPED
[INFO] Apache Jena - SPARQL Text Search - Elasticsearch ... SKIPPED
[INFO] Apache Jena - SPARQL Spatial Search ................ SKIPPED
[INFO] Apache Jena - Fuseki - A SPARQL 1.1 Server ......... SKIPPED
[INFO] Apache Jena - Fuseki Server Engine ................. SKIPPED
[INFO] Apache Jena - Fuseki Embedded Server ............... SKIPPED
[INFO] Apache Jena - Fuseki WAR File ...................... SKIPPED
[INFO] Apache Jena - Fuseki Server Standalone Jar ......... SKIPPED
[INFO] Apache Jena - Fuseki Basic Server .................. SKIPPED
[INFO] Apache Jena - Fuseki Binary Distribution ........... SKIPPED
[INFO] Apache Jena - Integration Testing .................. SKIPPED
[INFO] Apache Jena - Distribution ......................... SKIPPED
[INFO] Apache Jena - Fuseki1 .............................. SKIPPED
[INFO] Apache Jena - Data Tables for RDF and SPARQL ....... SKIPPED
[INFO] Apache Jena - SDB (SQL based triple store) ......... SKIPPED
[INFO] Apache Jena - Security Permissions ................. SKIPPED
[INFO] Apache Jena - Extras ............................... SKIPPED
[INFO] Apache Jena - Extras - Query Builder ............... SKIPPED
[INFO] Apache Jena - JDBC Parent .......................... SKIPPED
[INFO] Apache Jena - JDBC Core API ........................ SKIPPED
[INFO] Apache Jena - JDBC Remote Endpoint Driver .......... SKIPPED
[INFO] Apache Jena - JDBC In-Memory Driver ................ SKIPPED
[INFO] Apache Jena - JDBC TDB Driver ...................... SKIPPED
[INFO] Apache Jena - JDBC Driver Bundle ................... SKIPPED
[INFO] Apache Jena - Elephas .............................. SKIPPED
[INFO] Apache Jena - Elephas - Common API ................. SKIPPED
[INFO] Apache Jena - Elephas - I/O ........................ SKIPPED
[INFO] Apache Jena - Elephas - Map/Reduce ................. SKIPPED
[INFO] Apache Jena - Elephas - Statistics Demo App ........ SKIPPED
[INFO] Apache Jena - OSGi ................................. SKIPPED
[INFO] Apache Jena - OSGi bundle .......................... SKIPPED
[INFO] Apache Jena - OSGi Karaf features 3.7.0 ............ SKIPPED
[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 02:29 min
[INFO] Finished at: 2018-04-05T09:18:46+01:00
[INFO]
------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar (attach-javadocs)
on project jena-cmds: Execution attach-javadocs of goal
org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar failed.:
NullPointerException -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar
(attach-javadocs) on project jena-cmds: Execution attach-javadocs of goal
org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar failed.
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:213)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:154)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:146)
    at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:117)
    at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:81)
    at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
(SingleThreadedBuilder.java:56)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
(LifecycleStarter.java:128)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
    at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
    at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke (Method.java:498)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
(Launcher.java:289)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch
(Launcher.java:229)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
(Launcher.java:415)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main
(Launcher.java:356)
Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
attach-javadocs of goal
org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar failed.
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
(DefaultBuildPluginManager.java:148)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:208)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:154)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:146)
    at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:117)
    at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:81)
    at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
(SingleThreadedBuilder.java:56)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
(LifecycleStarter.java:128)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
    at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
    at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke (Nativ[INFO] ---
maven-javadoc-plugin:3.0.0:jar (attach-javadocs) @ jena-base ---
[INFO] The goal
'org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:javadoc' has not been
previously called for the module:
'org.apache.jena:jena-shaded-guava:jar:3.7.0'. Trying to invoke it...
[WARNING] Creating fake javadoc directory to prevent repeated invocations:
/home/claude/git/jena/jena-shaded-guava/target/apidocs
[INFO]
------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Jena 3.7.0 .................................. SUCCESS [
1.287 s]
[INFO] Apache Jena - Shadowed external libraries .......... SUCCESS [
1.504 s]
[INFO] Apache Jena - IRI .................................. SUCCESS [
2.575 s]
[INFO] Apache Jena - Base Common Environment .............. FAILURE [
3.921 s]
[INFO] Apache Jena - Core ................................. SKIPPED
[INFO] Apache Jena - ARQ (SPARQL 1.1 Query Engine) ........ SKIPPED
[INFO] Apache Jena - RDF Connection ....................... SKIPPED
[INFO] Apache Jena - TDB1 (Native Triple Store) ........... SKIPPED
[INFO] Apache Jena - Database Operation Environment ....... SKIPPED
[INFO] Apache Jena - DBOE Base ............................ SKIPPED
[INFO] Apache Jena - DBOE Transactions .................... SKIPPED
[INFO] Apache Jena - DBOE Indexes ......................... SKIPPED
[INFO] Apache Jena - DBOE Index test suite ................ SKIPPED
[INFO] Apache Jena - DBOE Transactional Datastructures .... SKIPPED
[INFO] Apache Jena - TDB2 ................................. SKIPPED
[INFO] Apache Jena - Libraries POM ........................ SKIPPED
[INFO] Apache Jena - Command line tools ................... SKIPPED
[INFO] Apache Jena - SPARQL Text Search ................... SKIPPED
[INFO] Apache Jena - SPARQL Text Search - Elasticsearch ... SKIPPED
[INFO] Apache Jena - SPARQL Spatial Search ................ SKIPPED
[INFO] Apache Jena - Fuseki - A SPARQL 1.1 Server ......... SKIPPED
[INFO] Apache Jena - Fuseki Server Engine ................. SKIPPED
[INFO] Apache Jena - Fuseki Embedded Server ............... SKIPPED
[INFO] Apache Jena - Fuseki WAR File ...................... SKIPPED
[INFO] Apache Jena - Fuseki Server Standalone Jar ......... SKIPPED
[INFO] Apache Jena - Fuseki Basic Server .................. SKIPPED
[INFO] Apache Jena - Fuseki Binary Distribution ........... SKIPPED
[INFO] Apache Jena - Integration Testing .................. SKIPPED
[INFO] Apache Jena - Distribution ......................... SKIPPED
[INFO] Apache Jena - Fuseki1 .............................. SKIPPED
[INFO] Apache Jena - Data Tables for RDF and SPARQL ....... SKIPPED
[INFO] Apache Jena - SDB (SQL based triple store) ......... SKIPPED
[INFO] Apache Jena - Security Permissions ................. SKIPPED
[INFO] Apache Jena - Extras ............................... SKIPPED
[INFO] Apache Jena - Extras - Query Builder ............... SKIPPED
[INFO] Apache Jena - JDBC Parent .......................... SKIPPED
[INFO] Apache Jena - JDBC Core API ........................ SKIPPED
[INFO] Apache Jena - JDBC Remote Endpoint Driver .......... SKIPPED
[INFO] Apache Jena - JDBC In-Memory Driver ................ SKIPPED
[INFO] Apache Jena - JDBC TDB Driver ...................... SKIPPED
[INFO] Apache Jena - JDBC Driver Bundle ................... SKIPPED
[INFO] Apache Jena - Elephas .............................. SKIPPED
[INFO] Apache Jena - Elephas - Common API ................. SKIPPED
[INFO] Apache Jena - Elephas - I/O ........................ SKIPPED
[INFO] Apache Jena - Elephas - Map/Reduce ................. SKIPPED
[INFO] Apache Jena - Elephas - Statistics Demo App ........ SKIPPED
[INFO] Apache Jena - OSGi ................................. SKIPPED
[INFO] Apache Jena - OSGi bundle .......................... SKIPPED
[INFO] Apache Jena - OSGi Karaf features 3.7.0 ............ SKIPPED
[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 10.059 s
[INFO] Finished at: 2018-04-05T09:14:17+01:00
[INFO]
------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar (attach-javadocs)
on project jena-base: Execution attach-javadocs of goal
org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar failed.:
NullPointerException -> [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 :jena-base
eMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke (Method.java:498)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
(Launcher.java:289)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch
(Launcher.java:229)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
(Launcher.java:415)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main
(Launcher.java:356)
Caused by: java.lang.NullPointerException
    at java.io.File.<init> (File.java:277)
    at org.apache.maven.plugins.javadoc.JavadocUtil.getJavaHome
(JavadocUtil.java:1302)
    at org.apache.maven.plugins.javadoc.JavadocUtil.invokeMaven
(JavadocUtil.java:941)
    at org.apache.maven.plugins.javadoc.AbstractJavadocMojo.getModulesLinks
(AbstractJavadocMojo.java:5620)
    at
org.apache.maven.plugins.javadoc.AbstractJavadocMojo.addLinkofflineArguments
(AbstractJavadocMojo.java:4026)
    at
org.apache.maven.plugins.javadoc.AbstractJavadocMojo.addStandardDocletOptions
(AbstractJavadocMojo.java:4916)
    at org.apache.maven.plugins.javadoc.AbstractJavadocMojo.executeReport
(AbstractJavadocMojo.java:2074)
    at org.apache.maven.plugins.javadoc.JavadocJar.doExecute
(JavadocJar.java:190)
    at org.apache.maven.plugins.javadoc.AbstractJavadocMojo.execute
(AbstractJavadocMojo.java:1909)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
(DefaultBuildPluginManager.java:137)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:208)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:154)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:146)
    at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:117)
    at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:81)
    at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
(SingleThreadedBuilder.java:56)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
(LifecycleStarter.java:128)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
    at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
    at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke (Method.java:498)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
(Launcher.java:289)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch
(Launcher.java:229)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
(Launcher.java:415)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main
(Launcher.java:356)
[ERROR]
[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 :jena-cmds


I think this only appears on a clean system with no previous build.  I am
doing this outside of an IDE and using Maven alone.

claude@claude-XPS-15-9560:~/git/jena$ java -version
openjdk version "1.8.0_162"
OpenJDK Runtime Environment (build 1.8.0_162-8u162-b12-0ubuntu0.16.04.2-b12)
OpenJDK 64-Bit Server VM (build 25.162-b12, mixed mode)
claude@claude-XPS-15-9560:~/git/jena$ mvn -version
Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297;
2018-02-24T19:49:05Z)
Maven home: /usr/share/apache-maven-3.5.3
Java version: 1.8.0_162, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-8-openjdk-amd64/jre
Default locale: en_IE, platform encoding: UTF-8
OS name: "linux", version: "4.13.0-37-generic", arch: "amd64", family:
"unix"
claude@claude-XPS-15-9560:~/git/jena$ uname -a
Linux claude-XPS-15-9560 4.13.0-37-generic #42~16.04.1-Ubuntu SMP Wed Mar 7
16:03:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
claude@claude-XPS-15-9560:~/git/jena$

Claude

On Wed, Apr 4, 2018 at 4:17 PM, Andy Seaborne <an...@apache.org> wrote:

> There is a fix in PR#391.
>
> I've run the test case umpteen times now without incident and done
> performance times of bulkloading, which is about as write intensive as it
> gets.
>
> The worse slow down I observed (difference of a 3.6 and 3.7-fix) when
> loading 25M BSBM triples was 3%.  Usually it's 1%. Larger loads will be
> dominated by I/O costs so what is a CPU-related fix will be overtaken (I
> hope!). It did in the testing I did.
>
> So this email cancels RC1 and I'll start again.
>
>      Andy
>
>
> On 03/04/18 23:01, Andy Seaborne wrote:
>
>> JENA-1516 looks serious and fixable.
>>
>> I'd like time to verify the fix that I have. As is often the case,
>> finding the concurrency problem is a lot more time consuming than fixing an
>> identified problem.
>>
>> The WIP fix is available at
>>    https://github.com/afs/jena/tree/jena-1516_ObjectFileStorage
>> if you are really interested.
>>
>> If that fix looks good, I propose cancelling this RC and doing a new one
>> to include the fix.
>>
>> If the fix does not look good, and it has taken quite a heavy sustained
>> concurrent load to get anything to go wrong (carefully parallel 100
>> updates, 100 queries, 50 threads and it still does not happen every time),
>> it seems better to continue RC1 and get a good fix done.
>>
>> Adam, Chris - thank you for the time to assess RC1.  There should be very
>> little change between RC1 and a possible RC2.
>>
>> (not sure if SUSPENDED is a recognized state for a VOTE - think of it as
>> the RM needs time to do some more checking)
>>
>>      Andy
>>
>> On 29/03/18 19:28, Andy Seaborne wrote:
>>
>>> Hi,
>>>
>>> Here is a vote on a release of Jena 3.7.0.
>>>
>>> This is the first proposed candidate for a 3.7.0 release.
>>>
>>> There are process changes.
>>>
>>> Deadline:
>>>
>>>         2018-04-01 22:00 UTC
>>>
>>> April 1st!
>>>
>>> ==== Process Changes
>>>
>>> 1/
>>> MD5 files are being discouraged because MD5 is not secure.  Projects are
>>> now asked to not publish md5.
>>>
>>> There are no md5 files in the proposed dist/jena area - files on Apache
>>> hardware.
>>>
>>> There are sha1 and sha512 checksums.
>>> * The sha512 is in Linux sha512sum checkable format.
>>> * The sha1 is whatever maven generated and is the same as will go to
>>> maven central.
>>>
>>> Having the sha1 ties the dist/jena artifacts to maven central (as does
>>> the .asc).
>>>
>>> There are md5 and sha1 in the proposes maven repo staging area for
>>> sending to maven central. That part of maven is hardwired to md5/sha1 still.
>>>
>>> There's a script to setup the sha512.
>>>
>>> 2/
>>> To establish the proof chain for signed artifacts in /dist/project/, I
>>> have been asked to try out the new META files.
>>>
>>> https://checker.apache.org/doc/README.html#ch-meta
>>>
>>> There are two files
>>>
>>> /dist/jena/META
>>> /dist/jena/META.asc
>>>
>>> META says who signs what, and is itself signed by the PMC chair.
>>>
>>> ==== Release changes
>>>
>>> 55 JIRA:
>>> https://s.apache.org/jena-3.7.0-jira
>>>
>>> == Significant Changes
>>>
>>> ** Java9: Building and running on a Java9 platform is supported
>>>
>>> JENA-1461 - Allow ARQ custom functions to be written in JavaScript
>>>
>>> JENA-1389 - Return `this` rather than `void` from Dataset (API change)
>>> JENA-1495 - Return Model from PrefixMapping methods (API change)
>>>
>>> JENA-1458, JENA-1483 - Transaction Promotion
>>>
>>> JENA-1453 - Lucene indexes using a graph field are smaller
>>>
>>> JENA-1490 - Working with Blank Nodes with Fuseki
>>>
>>> == Upgrades to libraries (runtime dependencies):
>>>
>>> No dependency changes.
>>>
>>> ==== Release Vote
>>>
>>> Everyone, not just committers, is invited to test and vote.
>>> Please download and test the proposed release.
>>>
>>> Proposed dist/ area:
>>>    https://dist.apache.org/repos/dist/dev/jena/
>>>
>>> Keys:
>>>    https://svn.apache.org/repos/asf/jena/dist/KEYS
>>>
>>> Staging repository:
>>>    https://repository.apache.org/content/repositories/orgapache
>>> jena-1022/
>>>
>>> Git commit (browser URL):
>>> https://git1-us-west.apache.org/repos/asf?p=jena.git;a=commit;h=d4e7063e
>>>
>>> Git Commit Hash:
>>>    d4e7063e7a6db8ce77699bd0388e1a1bd6816626
>>>
>>> Git Commit Tag:
>>>       jena-3.7.0-rc1
>>>
>>> Please vote to approve this release:
>>>
>>>         [ ] +1 Approve the release
>>>         [ ]  0 Don't care
>>>         [ ] -1 Don't release, because ...
>>>
>>> This vote will be open until at least
>>>
>>>         2018-04-01 22:00 UTC
>>>
>>> If you expect to check the release but the time 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?
>>>
>>


-- 
I like: Like Like - The likeliest place on the web
<http://like-like.xenei.com>
LinkedIn: http://www.linkedin.com/in/claudewarren

Re: [CANCELLED] Apache Jena 3.7.0 RC1

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

There is a fix in PR#391.

I've run the test case umpteen times now without incident and done 
performance times of bulkloading, which is about as write intensive as 
it gets.

The worse slow down I observed (difference of a 3.6 and 3.7-fix) when 
loading 25M BSBM triples was 3%.  Usually it's 1%. Larger loads will be 
dominated by I/O costs so what is a CPU-related fix will be overtaken (I 
hope!). It did in the testing I did.

So this email cancels RC1 and I'll start again.

      Andy

On 03/04/18 23:01, Andy Seaborne wrote:
> JENA-1516 looks serious and fixable.
> 
> I'd like time to verify the fix that I have. As is often the case, 
> finding the concurrency problem is a lot more time consuming than fixing 
> an identified problem.
> 
> The WIP fix is available at
>    https://github.com/afs/jena/tree/jena-1516_ObjectFileStorage
> if you are really interested.
> 
> If that fix looks good, I propose cancelling this RC and doing a new one 
> to include the fix.
> 
> If the fix does not look good, and it has taken quite a heavy sustained 
> concurrent load to get anything to go wrong (carefully parallel 100 
> updates, 100 queries, 50 threads and it still does not happen every 
> time), it seems better to continue RC1 and get a good fix done.
> 
> Adam, Chris - thank you for the time to assess RC1.  There should be 
> very little change between RC1 and a possible RC2.
> 
> (not sure if SUSPENDED is a recognized state for a VOTE - think of it as 
> the RM needs time to do some more checking)
> 
>      Andy
> 
> On 29/03/18 19:28, Andy Seaborne wrote:
>> Hi,
>>
>> Here is a vote on a release of Jena 3.7.0.
>>
>> This is the first proposed candidate for a 3.7.0 release.
>>
>> There are process changes.
>>
>> Deadline:
>>
>>         2018-04-01 22:00 UTC
>>
>> April 1st!
>>
>> ==== Process Changes
>>
>> 1/
>> MD5 files are being discouraged because MD5 is not secure.  Projects 
>> are now asked to not publish md5.
>>
>> There are no md5 files in the proposed dist/jena area - files on 
>> Apache hardware.
>>
>> There are sha1 and sha512 checksums.
>> * The sha512 is in Linux sha512sum checkable format.
>> * The sha1 is whatever maven generated and is the same as will go to 
>> maven central.
>>
>> Having the sha1 ties the dist/jena artifacts to maven central (as does 
>> the .asc).
>>
>> There are md5 and sha1 in the proposes maven repo staging area for 
>> sending to maven central. That part of maven is hardwired to md5/sha1 
>> still.
>>
>> There's a script to setup the sha512.
>>
>> 2/
>> To establish the proof chain for signed artifacts in /dist/project/, I 
>> have been asked to try out the new META files.
>>
>> https://checker.apache.org/doc/README.html#ch-meta
>>
>> There are two files
>>
>> /dist/jena/META
>> /dist/jena/META.asc
>>
>> META says who signs what, and is itself signed by the PMC chair.
>>
>> ==== Release changes
>>
>> 55 JIRA:
>> https://s.apache.org/jena-3.7.0-jira
>>
>> == Significant Changes
>>
>> ** Java9: Building and running on a Java9 platform is supported
>>
>> JENA-1461 - Allow ARQ custom functions to be written in JavaScript
>>
>> JENA-1389 - Return `this` rather than `void` from Dataset (API change)
>> JENA-1495 - Return Model from PrefixMapping methods (API change)
>>
>> JENA-1458, JENA-1483 - Transaction Promotion
>>
>> JENA-1453 - Lucene indexes using a graph field are smaller
>>
>> JENA-1490 - Working with Blank Nodes with Fuseki
>>
>> == Upgrades to libraries (runtime dependencies):
>>
>> No dependency changes.
>>
>> ==== Release Vote
>>
>> Everyone, not just committers, is invited to test and vote.
>> Please download and test the proposed release.
>>
>> Proposed dist/ area:
>>    https://dist.apache.org/repos/dist/dev/jena/
>>
>> Keys:
>>    https://svn.apache.org/repos/asf/jena/dist/KEYS
>>
>> Staging repository:
>>    https://repository.apache.org/content/repositories/orgapachejena-1022/
>>
>> Git commit (browser URL):
>> https://git1-us-west.apache.org/repos/asf?p=jena.git;a=commit;h=d4e7063e
>>
>> Git Commit Hash:
>>    d4e7063e7a6db8ce77699bd0388e1a1bd6816626
>>
>> Git Commit Tag:
>>       jena-3.7.0-rc1
>>
>> Please vote to approve this release:
>>
>>         [ ] +1 Approve the release
>>         [ ]  0 Don't care
>>         [ ] -1 Don't release, because ...
>>
>> This vote will be open until at least
>>
>>         2018-04-01 22:00 UTC
>>
>> If you expect to check the release but the time 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: [SUSPENDED] Apache Jena 3.7.0 RC1

Posted by Claude Warren <cl...@xenei.com>.

My home system has crashed and I am not at work tomorrow so i will be
offline for the next 36 hrs or so.

On 3 Apr 2018 23:01, "Andy Seaborne" <an...@apache.org> wrote:

> JENA-1516 looks serious and fixable.
>
> I'd like time to verify the fix that I have. As is often the case, finding
> the concurrency problem is a lot more time consuming than fixing an
> identified problem.
>
> The WIP fix is available at
>   https://github.com/afs/jena/tree/jena-1516_ObjectFileStorage
> if you are really interested.
>
> If that fix looks good, I propose cancelling this RC and doing a new one
> to include the fix.
>
> If the fix does not look good, and it has taken quite a heavy sustained
> concurrent load to get anything to go wrong (carefully parallel 100
> updates, 100 queries, 50 threads and it still does not happen every time),
> it seems better to continue RC1 and get a good fix done.
>
> Adam, Chris - thank you for the time to assess RC1.  There should be very
> little change between RC1 and a possible RC2.
>
> (not sure if SUSPENDED is a recognized state for a VOTE - think of it as
> the RM needs time to do some more checking)
>
>     Andy
>
> On 29/03/18 19:28, Andy Seaborne wrote:
>
>> Hi,
>>
>> Here is a vote on a release of Jena 3.7.0.
>>
>> This is the first proposed candidate for a 3.7.0 release.
>>
>> There are process changes.
>>
>> Deadline:
>>
>>         2018-04-01 22:00 UTC
>>
>> April 1st!
>>
>> ==== Process Changes
>>
>> 1/
>> MD5 files are being discouraged because MD5 is not secure.  Projects are
>> now asked to not publish md5.
>>
>> There are no md5 files in the proposed dist/jena area - files on Apache
>> hardware.
>>
>> There are sha1 and sha512 checksums.
>> * The sha512 is in Linux sha512sum checkable format.
>> * The sha1 is whatever maven generated and is the same as will go to
>> maven central.
>>
>> Having the sha1 ties the dist/jena artifacts to maven central (as does
>> the .asc).
>>
>> There are md5 and sha1 in the proposes maven repo staging area for
>> sending to maven central. That part of maven is hardwired to md5/sha1 still.
>>
>> There's a script to setup the sha512.
>>
>> 2/
>> To establish the proof chain for signed artifacts in /dist/project/, I
>> have been asked to try out the new META files.
>>
>> https://checker.apache.org/doc/README.html#ch-meta
>>
>> There are two files
>>
>> /dist/jena/META
>> /dist/jena/META.asc
>>
>> META says who signs what, and is itself signed by the PMC chair.
>>
>> ==== Release changes
>>
>> 55 JIRA:
>> https://s.apache.org/jena-3.7.0-jira
>>
>> == Significant Changes
>>
>> ** Java9: Building and running on a Java9 platform is supported
>>
>> JENA-1461 - Allow ARQ custom functions to be written in JavaScript
>>
>> JENA-1389 - Return `this` rather than `void` from Dataset (API change)
>> JENA-1495 - Return Model from PrefixMapping methods (API change)
>>
>> JENA-1458, JENA-1483 - Transaction Promotion
>>
>> JENA-1453 - Lucene indexes using a graph field are smaller
>>
>> JENA-1490 - Working with Blank Nodes with Fuseki
>>
>> == Upgrades to libraries (runtime dependencies):
>>
>> No dependency changes.
>>
>> ==== Release Vote
>>
>> Everyone, not just committers, is invited to test and vote.
>> Please download and test the proposed release.
>>
>> Proposed dist/ area:
>>    https://dist.apache.org/repos/dist/dev/jena/
>>
>> Keys:
>>    https://svn.apache.org/repos/asf/jena/dist/KEYS
>>
>> Staging repository:
>>    https://repository.apache.org/content/repositories/orgapachejena-1022/
>>
>> Git commit (browser URL):
>> https://git1-us-west.apache.org/repos/asf?p=jena.git;a=commit;h=d4e7063e
>>
>> Git Commit Hash:
>>    d4e7063e7a6db8ce77699bd0388e1a1bd6816626
>>
>> Git Commit Tag:
>>       jena-3.7.0-rc1
>>
>> Please vote to approve this release:
>>
>>         [ ] +1 Approve the release
>>         [ ]  0 Don't care
>>         [ ] -1 Don't release, because ...
>>
>> This vote will be open until at least
>>
>>         2018-04-01 22:00 UTC
>>
>> If you expect to check the release but the time 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: [SUSPENDED] Apache Jena 3.7.0 RC1

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

JENA-1516 looks serious and fixable.

I'd like time to verify the fix that I have. As is often the case, 
finding the concurrency problem is a lot more time consuming than fixing 
an identified problem.

The WIP fix is available at
   https://github.com/afs/jena/tree/jena-1516_ObjectFileStorage
if you are really interested.

If that fix looks good, I propose cancelling this RC and doing a new one 
to include the fix.

If the fix does not look good, and it has taken quite a heavy sustained 
concurrent load to get anything to go wrong (carefully parallel 100 
updates, 100 queries, 50 threads and it still does not happen every 
time), it seems better to continue RC1 and get a good fix done.

Adam, Chris - thank you for the time to assess RC1.  There should be 
very little change between RC1 and a possible RC2.

(not sure if SUSPENDED is a recognized state for a VOTE - think of it as 
the RM needs time to do some more checking)

     Andy

On 29/03/18 19:28, Andy Seaborne wrote:
> Hi,
> 
> Here is a vote on a release of Jena 3.7.0.
> 
> This is the first proposed candidate for a 3.7.0 release.
> 
> There are process changes.
> 
> Deadline:
> 
>         2018-04-01 22:00 UTC
> 
> April 1st!
> 
> ==== Process Changes
> 
> 1/
> MD5 files are being discouraged because MD5 is not secure.  Projects are 
> now asked to not publish md5.
> 
> There are no md5 files in the proposed dist/jena area - files on Apache 
> hardware.
> 
> There are sha1 and sha512 checksums.
> * The sha512 is in Linux sha512sum checkable format.
> * The sha1 is whatever maven generated and is the same as will go to 
> maven central.
> 
> Having the sha1 ties the dist/jena artifacts to maven central (as does 
> the .asc).
> 
> There are md5 and sha1 in the proposes maven repo staging area for 
> sending to maven central. That part of maven is hardwired to md5/sha1 
> still.
> 
> There's a script to setup the sha512.
> 
> 2/
> To establish the proof chain for signed artifacts in /dist/project/, I 
> have been asked to try out the new META files.
> 
> https://checker.apache.org/doc/README.html#ch-meta
> 
> There are two files
> 
> /dist/jena/META
> /dist/jena/META.asc
> 
> META says who signs what, and is itself signed by the PMC chair.
> 
> ==== Release changes
> 
> 55 JIRA:
> https://s.apache.org/jena-3.7.0-jira
> 
> == Significant Changes
> 
> ** Java9: Building and running on a Java9 platform is supported
> 
> JENA-1461 - Allow ARQ custom functions to be written in JavaScript
> 
> JENA-1389 - Return `this` rather than `void` from Dataset (API change)
> JENA-1495 - Return Model from PrefixMapping methods (API change)
> 
> JENA-1458, JENA-1483 - Transaction Promotion
> 
> JENA-1453 - Lucene indexes using a graph field are smaller
> 
> JENA-1490 - Working with Blank Nodes with Fuseki
> 
> == Upgrades to libraries (runtime dependencies):
> 
> No dependency changes.
> 
> ==== Release Vote
> 
> Everyone, not just committers, is invited to test and vote.
> Please download and test the proposed release.
> 
> Proposed dist/ area:
>    https://dist.apache.org/repos/dist/dev/jena/
> 
> Keys:
>    https://svn.apache.org/repos/asf/jena/dist/KEYS
> 
> Staging repository:
>    https://repository.apache.org/content/repositories/orgapachejena-1022/
> 
> Git commit (browser URL):
> https://git1-us-west.apache.org/repos/asf?p=jena.git;a=commit;h=d4e7063e
> 
> Git Commit Hash:
>    d4e7063e7a6db8ce77699bd0388e1a1bd6816626
> 
> Git Commit Tag:
>       jena-3.7.0-rc1
> 
> Please vote to approve this release:
> 
>         [ ] +1 Approve the release
>         [ ]  0 Don't care
>         [ ] -1 Don't release, because ...
> 
> This vote will be open until at least
> 
>         2018-04-01 22:00 UTC
> 
> If you expect to check the release but the time 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?