[07/50] tinkerpop git commit: HADOOP_GREMLIN_LIBS does not need "spark"

2017-02-15 Thread spmallette
HADOOP_GREMLIN_LIBS does not need "spark" This causes more problems in 3.3.0 where Spark 2.0 generates errors if duplicate jars are on the path. Having "spark-gremlin" with "hadoop-gremlin" immediately causes problems. CTR Project: http://git-wip-us.apache.org/repos/asf/tinkerpop/repo Commit:

[30/45] tinkerpop git commit: HADOOP_GREMLIN_LIBS does not need "spark"

2017-01-30 Thread spmallette
HADOOP_GREMLIN_LIBS does not need "spark" This causes more problems in 3.3.0 where Spark 2.0 generates errors if duplicate jars are on the path. Having "spark-gremlin" with "hadoop-gremlin" immediately causes problems. CTR Project: http://git-wip-us.apache.org/repos/asf/tinkerpop/repo Commit:

tinkerpop git commit: HADOOP_GREMLIN_LIBS does not need "spark"

2017-01-30 Thread spmallette
Repository: tinkerpop Updated Branches: refs/heads/tp32 5aa3f40db -> 8f34da823 HADOOP_GREMLIN_LIBS does not need "spark" This causes more problems in 3.3.0 where Spark 2.0 generates errors if duplicate jars are on the path. Having "spark-gremlin" with "hadoop-gremlin" immediately causes

[1/2] tinkerpop git commit: HADOOP_GREMLIN_LIBS does not need "spark"

2017-01-30 Thread spmallette
Repository: tinkerpop Updated Branches: refs/heads/master a98fb132e -> b7aa94859 HADOOP_GREMLIN_LIBS does not need "spark" This causes more problems in 3.3.0 where Spark 2.0 generates errors if duplicate jars are on the path. Having "spark-gremlin" with "hadoop-gremlin" immediately causes