[ 
https://issues.apache.org/jira/browse/TINKERPOP3-858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14941411#comment-14941411
 ] 

stephen mallette commented on TINKERPOP3-858:
---------------------------------------------

[~pluradj] said he was going to take a look at this one.  Here's some pointers 
to ease your work.  For the console, I believe some additional logic here to 
"clean up" should solve the problem:

https://github.com/apache/incubator-tinkerpop/blob/master/gremlin-console/src/main/groovy/org/apache/tinkerpop/gremlin/console/commands/InstallCommand.groovy#L56

for the server, similar logic would need to be injected here:

https://github.com/apache/incubator-tinkerpop/blob/master/gremlin-server/src/main/java/org/apache/tinkerpop/gremlin/server/util/GremlinServerInstall.java#L40

I think it's that simple - hopefully it's not a bigger deal than that.  Not 
sure that you can easily write tests for this stuff, but if you can come up 
with something that would be nice.  

> Cleanup after failed :install
> -----------------------------
>
>                 Key: TINKERPOP3-858
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP3-858
>             Project: TinkerPop 3
>          Issue Type: Improvement
>          Components: console, server
>    Affects Versions: 3.0.1-incubating
>            Reporter: stephen mallette
>            Assignee: stephen mallette
>            Priority: Minor
>             Fix For: 3.0.2-incubating
>
>
> If {{:install}} tanks:
> {code}
> gremlin> :install org.apache.tinkerpop hadoop-gremlin 3.1.0-SNAPSHOT
> ==>Error grabbing Grapes -- [download failed: 
> io.netty#netty;3.6.2.Final!netty.jar(bundle)]
> {code}
> try to clean up the directory that gets created or else future attempts do 
> this:
> {code}
> gremlin> :install org.apache.tinkerpop hadoop-gremlin 3.1.0-SNAPSHOT
> ==>a module with the name hadoop-gremlin is already installed
> {code}
> This is also a problem for {{bin/gremlin-server.sh -i}}



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

Reply via email to