-1 (binding)
We need add RYA-370 since it fixes the optionalness of the GPL Geo
libraries, and a couple other little issues.
We did that already (PR is out there, thanks Jeff!). Now we should go
ahead and make the benchmarks optional, and Giraph optional (see below),
since we get big benefit for
4:54 PM
To: dev@rya.incubator.apache.org
Subject: Re: [VOTE] Release Rya (Incubating) version 3.2.11 RC2
-1 (binding)
The incorporation of bad licensing has the potential to limit where Rya can be
deployed. I would like to see following addressed:
https://urldefense.proofpoint.com/v2/url?u=
-1 (binding)
The incorporation of bad licensing has the potential to limit where Rya can be
deployed. I would like to see following addressed:
https://issues.apache.org/jira/browse/RYA-372 Replace org.json:json library
with a compatibly licensed alternative
https://issues.apache.org/jira/brow
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
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 the
> , 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.
https://
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:
> It is fine to no
It is fine to not to release the geoindexing artifacts, but we need all of
the pom version strings to be consistent (and correct) so that if one did
want to build them with the geoindexing profile, they can.
Speaking of artifacts, nexus seems to have a lot of geoindexing artifacts
in it. Probably
Don't we not release the geoindexing artifacts? Sorry if I'm being slow here
Sent from my iPhone
> On Sep 12, 2017, at 5:23 PM, Jeff Dasch wrote:
>
> -1 (non-binding)
>
> The pom for rya.pcj.functions.geo references a parent artifact with a
> 3.2.11-incubating-SNAPSHOT version:
> grep -r 3.2.1
-1 (non-binding)
The pom for rya.pcj.functions.geo references a parent artifact with a
3.2.11-incubating-SNAPSHOT version:
grep -r 3.2.11-incubating-SNAPSHOT rya-project-3.2.11-incubating
rya-project-3.2.11-incubating/extras/rya.pcj.fluo/rya.pcj.functions.geo/pom.xml:
3.2.11-incubating-SNAPSHOT
N
10 matches
Mail list logo