[
https://issues.apache.org/jira/browse/GROOVY-4300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14982984#comment-14982984
]
Mark Fortner commented on GROOVY-4300:
--------------------------------------
Thanks, John. I'm aware of a couple of repositories like that including
bintray. It would be really useful though, if it were possible to search
across these repositories for specific libraries and then include them in your
script. There are often workarounds for a variety of problems, but I find that
the easier that you make it for a user to get something done, the more likely
they are to use it. The Groovy Console is a great tool, and a great on-ramp to
the Groovy language for a lot of beginners, and anything that can be done to
make it easier to use will undoubtedly make Groovy more approachable.
The other thing I wonder, is whether or not the Grape mechanism could be used
to extend the Groovy console functionality with new plugins? I could imagine
wanting to be able to import Excel data and graph it.
> Add Grape Catalog To Groovy Console
> -----------------------------------
>
> Key: GROOVY-4300
> URL: https://issues.apache.org/jira/browse/GROOVY-4300
> Project: Groovy
> Issue Type: Improvement
> Components: Grape, Groovy Console
> Reporter: Mark Fortner
> Labels: contrib
>
> The Grape/Grab feature is one of the most useful features in Groovy.
> However, figuring out what modules, groups and versions to use in a script
> can be daunting. To make this easier on the user, I propose that a simple
> action be implemented which shows the available modules.
> The user would right-click inside the script they are writing and select a
> "Insert Grape" menu item.
> A dialog box would appear displaying either the locally available modules, or
> a combination of local and remote modules.
> The user would select the modules that they want to insert, and the action
> would insert the appropriate @Grab annotation into the script for each of the
> selected modules.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
