third party licenses examined for 3.2.11 RC2

2017-09-13 Thread David Lotts
​Here is my analysis of our third party licenses. Using this history as a guide: https://www.mail-archive.com/dev@rya.incubator.apache.org/msg00969.html and this : https://issues.apache.org/jira/browse/RYA-177 in order: the good, the bad, the to-do: ### BSD good from:

Re: [VOTE] Release Rya (Incubating) version 3.2.11 RC2

2017-09-13 Thread Josh Elser
Yep. For the same reason that geoindexing module cannot be built by default (requires the user to acknowledge that they're using a library with this license), the benchmark module cannot be built by default. Good catch folks. On 9/13/17 3:57 PM, Jeff Dasch wrote: Created RYA-370 to track the

Re: [VOTE] Release Rya (Incubating) version 3.2.11 RC2

2017-09-13 Thread Jeff Dasch
Created RYA-370 to track the geoindexing profile bug and the renaming recommendation. My finding wrt the sesame-runtime-osgi pom is covered by RYA-8. Ignoring that for now. Here's the current license check. Are there any issues with the GNU licenses here? Apache Giraph seems to be providing

Re: [VOTE] Release Rya (Incubating) version 3.2.11 RC2

2017-09-13 Thread David Lotts
> , nexus seems to have a lot of geoindexing > artifacts in it. Probably need to revist the extras/pom.xml as it > looks like there's a regression in there. The last release 3.2.10 has no geoindexing jars in Nexus. I see what you are saying. This release candidate has folders for each.

Re: [VOTE] Release Rya (Incubating) version 3.2.11 RC2

2017-09-13 Thread Jeff Dasch
Also, it appears that there is an issue with this project as well: grep -r 3.2.10-incubating-SNAPSHOT rya-project-3.2.11-incubating rya-project-3.2.11-incubating/osgi/sesame-runtime-osgi/pom.xml: *3.2.10-incubating-SNAPSHOT* On Wed, Sep 13, 2017 at 12:05 AM, Jeff Dasch wrote: