You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tinkerpop.apache.org by "Jason Plurad (JIRA)" <ji...@apache.org> on 2015/12/18 14:55:46 UTC

[jira] [Created] (TINKERPOP-1053) installed plugins are placed in a directory relative to where gremlin.sh is started

Jason Plurad created TINKERPOP-1053:
---------------------------------------

             Summary: 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.0.2-incubating, 3.1.0-incubating
            Reporter: Jason Plurad
            Assignee: Jason Plurad


>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 with $TP3_HOME/bin/gremlin.sh




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)