[
https://issues.apache.org/jira/browse/GROOVY-6514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14718374#comment-14718374
]
Thibault Kruse commented on GROOVY-6514:
----------------------------------------
Coming back to this, as discussed here,
http://groovy.329449.n5.nabble.com/groovysh-import-completion-for-Grape-loaded-classes-td5727025.html
I now think this should not be solved at startup, but during groovysh sessions.
I think a nice solution would be for Groovy to have a :grab command to get jars
via grapes, and ideally after doing so, the classes from the new jar should be
available in tab completion for the import command.
I implemented this here:
https://github.com/apache/incubator-groovy/pull/104
> 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)
