[jira] [Commented] (GROOVY-6514) groovysh should offer easier access to grapes

["Jake Gage (JIRA)" <ji...@apache.org>]

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

Jake Gage commented on GROOVY-6514:
-----------------------------------

I really love the above Pull (so much so that I abandoned a branch to implement a `:grab` command).  The only thing I don't understand is the impact to the change in Grape itself— I wonder if we wouldn't be better served with a delegate method here.

Hope this makes it in— for those who can't wait to see it, I created a [hack to tide myself over](https://github.com/Dispader/groovysh-command-grab).

> groovysh should offer easier access to grapes
> ---------------------------------------------
>
>                 Key: GROOVY-6514
>                 URL: https://issues.apache.org/jira/browse/GROOVY-6514
>             Project: Groovy
>          Issue Type: Improvement
>          Components: Groovysh
>            Reporter: Thibault Kruse
>            Priority: Minor
>
> groovysh can be started using a -cp option to use a given classpath. (BTW, the option is missing from the docs at http://groovy.codehaus.org/Groovy+Shell
> However it is rather cumbersome to use this mechanism to start groovysh to e.g. use a more convenient xml parser or such.
> So I can think of some solutions:
>  * add an option to use the latest of all libraries in ~/.groovy/grapes
>  * add an option to use specific grapes on startup, which would download those if necessary and then put them on the classpath
>  * provide a virtual environment tool that sets the classpath according to a definition file defining the grapes to be used.
> Thoughts?



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