[
http://jira.codehaus.org/browse/MGROOVY-149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=139968#action_139968
]
Tom Nichols commented on MGROOVY-149:
-------------------------------------
Exactly. Without a POM we might as well just run {{groovyConsole}} or
{{groovyShell}} straight from the command line without Maven. Is there a
reason to have a console/shell goal that _doesn't_ require a POM?
I suppose having the non-POM goals would just about obviate the need to
download the Groovy distribution at all...
> Add command to launch GroovyConsole and GroovyShell with POM dependencies on
> classpath
> --------------------------------------------------------------------------------------
>
> Key: MGROOVY-149
> URL: http://jira.codehaus.org/browse/MGROOVY-149
> Project: GMaven
> Issue Type: New Feature
> Components: tools
> Reporter: Tom Nichols
> Assignee: Jason Dillon
> Priority: Minor
> Fix For: 1.0-rc-3
>
>
> Or is it called a "goal" in Maven? I forget...
> re: [this Groovy-User
> thread|http://www.nabble.com/Groovy-Console-in-Groovy-Plugin-tp8332494p17786710.html]
> i.e.
> {quote}
> > mvn groovy:console
> {quote}
> launches GroovyConsole where the user has access to all of the POM's
> dependencies on the classpath
> Same for:
> {quote}
> > mvn groovy:shell
> {quote}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
