You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@groovy.apache.org by "Paul King (JIRA)" <ji...@apache.org> on 2017/05/02 02:03:09 UTC
[jira] [Closed] (GROOVY-6514) groovysh should offer easier access
to grapes
[ https://issues.apache.org/jira/browse/GROOVY-6514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul King closed GROOVY-6514.
-----------------------------
> 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
> Assignee: Pascal Schumacher
> Fix For: 2.5.0-alpha-1
>
>
> 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.15#6346)