If it's a runtime dependency, you are fine. Apache only supports source
releases. We vote on source tar ball and not binary artifacts.
Makes sense?
Sent from my iPhone,
Venkatesh
> On Oct 6, 2016, at 12:40 PM, David Lotts wrote:
>
> Yes, geotools is a runtime dependency.
I don't think that's acceptable. As you mentioned earlier, that is a large
portion of what Parsons has contributed to Rya.
Sent from my Verizon 4G LTE smartphone
Original message
From: "Aaron D. Mihalik"
Date: 10/6/16 10:16 PM (GMT-05:00)
To:
After reviewing the PR that David submitted, it's concerning the number of
projects that would fall into this "optional" bin. Some users probably
consider these "core" functions (e.g. reasoning and web):
Here the modules that need to be removed from the build in order to remove
the geotools
Yes, geotools is a runtime dependency. No geotools source code is
distributed.
By that I mean: Geotools source code is not in our source code repository.
Only references: imports in our *.java files and dependencies entries in
our pom.xml. Because of this maven will package geotools JARs
Quick question - geotools is a runtime dependency? Are you shipping the source
code? If not, you should be okay.
Sent from my iPhone,
Venkatesh
> On Oct 6, 2016, at 7:52 AM, Puja Valiyil wrote:
>
> Hi everyone,
> Talking with Aaron, it seems like there were two paths
Sure --
The indexing project includes the following optional features:
1. Temporal indexing
2. Free Text indexing
3. Pre-computed joins
4. Geo Indexing
5. Entity Centric Index
The main thing to keep in mind is that for all of these features, a user
has to explicitly turn them on in the
Puja, can you please detail what options are in the indexing project (for
option 1)? As Andrew asked, are pre-computed indices part of that project?
How about the entity-centric index? And is it correct that if we go with
option 1, there is still a reasonably easy way for people interested in the
Wouldn't that also take out precomputed joins? And are we absolutely sure we
don't want indexing? It seems important, couldn't we make geo optional?
Sent from my T-Mobile 4G LTE device
-- Original message--
From: Puja Valiyil
Date: Thu, Oct 6, 2016 10:52 AM
To:
Hi everyone,
Talking with Aaron, it seems like there were two paths forward for
refactoring in order to create a release. To refresh everyone's memory,
the issue was that the geo-indexing extensions to Rya pull in geotools,
which prohibits us from releasing Rya under an Apache 2 license. There