[ 
https://issues.apache.org/jira/browse/TINKERPOP-1053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

stephen mallette closed TINKERPOP-1053.
---------------------------------------
       Resolution: Fixed
         Assignee: stephen mallette  (was: Jason Plurad)
    Fix Version/s: 3.3.2
                   3.2.8

This is a really old issue and it appears to be resolved with gremlin.sh:

{code}
/bin$ ./gremlin.sh

         \,,,/
         (o o)
-----oOOo-(3)-oOOo-----
plugin activated: tinkerpop.server
plugin activated: tinkerpop.utilities
plugin activated: tinkerpop.tinkergraph
gremlin> :install org.apache.tinkerpop neo4j-gremlin 3.2.8-SNAPSHOT
==>Loaded: [org.apache.tinkerpop, neo4j-gremlin, 3.2.8-SNAPSHOT] - restart the 
console to use [tinkerpop.neo4j]
gremlin> :x
/bin$ ls
gremlin.bat  gremlin.sh  hadoop
/bin$ cd ..
$ ls
bin  conf  data  ext  lib
$ ls ext
gremlin-groovy  neo4j-gremlin  plugins.txt  README.txt  tinkergraph-gremlin
{code}

As you can see {{neo4j-gremlin}} is where it's supposed to be and not in the 
{{/bin}} directory. I have no idea when this was really fixed so I'll just 
assign to the current versions as where it was verified as being resolved.

> installed plugins are placed in a directory relative to where gremlin.sh is 
> started
> -----------------------------------------------------------------------------------
>
>                 Key: TINKERPOP-1053
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-1053
>             Project: TinkerPop
>          Issue Type: Bug
>          Components: console, server
>    Affects Versions: 3.1.0-incubating, 3.0.2-incubating
>            Reporter: Jason Plurad
>            Assignee: stephen mallette
>            Priority: Major
>             Fix For: 3.2.8, 3.3.2
>
>
> From mailing list discussion here 
> https://groups.google.com/d/msg/gremlin-users/4ooHKOXo7-w/1xmMQZvQCwAJ
> The problem is that if you start gremlin.sh from the $TP3_HOME/bin directory, 
> installed plugins end up under $TP3_HOME/bin/ext instead of under 
> $TP3_HOME/ext where existing plugins are located.
> The problem also exists with gremlin-server.sh plugins.
> The workaround is to start gremlin from $TP3_HOME with ./bin/gremlin.sh



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to