Steve, (sorry for late reply)
Neo4j can either be remote or embedded, and my guess is that TinkerPop is
looking for the embedded variant, since (IIRC) that is under GPL whereas
"remote" is the Enterprise version which is either commercial or AGPL
license.
I think it is great that Neo is intereste
neo4j is just a remote app in this context, right? So there'll be no classpath
contamination?
in which case, I don't see why there'd be any worry about pulling in to the
test/release process. I think having neo4j maintain the artifact makes sense
from a maintenance/release process, tinkerpop ca
Hello,
Here are notes to peoples comments thus far:
1. TinkerPop2 (prior to Apache) maintained all the vendor connectors.
This was very burdensome for the TinkerPop developers as we had to stay up to
date on each vendors changes. We didn't want to go down this road for
TinkerPop3 (now
Hi,
On Tue, Apr 28, 2015 at 5:33 PM, Marko Rodriguez wrote:
> ...In short, TinkerPop would depend on an Apache2 licensed neo4j-api. Some
> manual
> downloads from testers/users would be required to use the tinkerpop-neo4j
> component
> with a Neo4j database
That sounds ok to me as long as
On 30/04/2015 00:24, "Niclas Hedhman" wrote:
>But may I suggest the other way around?? Can't Neo4j have a Tinkerpop
>module at their end, which Tinkerpop advertise to be available for those
>that can live with the GPL/AGPL limitations? That would make this a
>non-issue, and IIUIC fits well withi
On Wed, Apr 29, 2015 at 7:25 PM Niclas Hedhman wrote:
> Well, for the End User, he/she can not use Tinkerpop+Neo4j without
> complying with GPL/AGPL.
> If Tinkerpop doesn't require Neo4j and still be useful, then that should be
> Ok.
> If Neo4j is essential to Tinkerpop, i.e. not useful without N
Well, for the End User, he/she can not use Tinkerpop+Neo4j without
complying with GPL/AGPL.
If Tinkerpop doesn't require Neo4j and still be useful, then that should be
Ok.
If Neo4j is essential to Tinkerpop, i.e. not useful without Neo4j, then
this is simply not acceptable.
Apache Zest has a simil
On Tue, Apr 28, 2015 at 11:34 AM Marko Rodriguez
wrote:
> Hello,
>
> TinkerPop (http://tinkerpop.incubator.apache.org/), prior to being an
> Apache project, provided a tinkerpop-neo4j adaptor with each release.
> TinkerPop sees Neo4j as the "reference OLTP implementation" of TinkerPop.
> With Tin
Hello,
TinkerPop (http://tinkerpop.incubator.apache.org/), prior to being an Apache
project, provided a tinkerpop-neo4j adaptor with each release. TinkerPop sees
Neo4j as the "reference OLTP implementation" of TinkerPop. With TinkerPop's
migration to the Apache Software Foundation, TinkerPop 3.
