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

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.1.0-incubating, 3.0.2-incubating
• Fix Version/s: 3.2.8, 3.3.2
• Component/s: console, server
• Assignee: Stephen Mallette
• Reporter: Jason Plurad
• Created: 18/Dec/15 13:55
• Updated: 16/Feb/18 13:21
• Resolved: 16/Feb/18 13:21

Description

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