[
http://jira.codehaus.org/browse/MGROOVY-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon closed MGROOVY-154.
--------------------------------
Resolution: Duplicate
> console/shell access to classes defined in the project
> ------------------------------------------------------
>
> Key: MGROOVY-154
> URL: http://jira.codehaus.org/browse/MGROOVY-154
> Project: GMaven
> Issue Type: New Feature
> Affects Versions: 1.0-rc-2
> Reporter: David Smiley
> Assignee: Jason Dillon
> Fix For: 1.0-rc-3
>
>
> I got GMaven and expected that it's "mvn groovy:console" & "mvn groovy:shell"
> features would automatically have my project's code (specifically, my project
> compiled plus any runtime dependencies) on the classpath. That isn't the
> case... and makes me wonder what's the point? If it doesn't even do that
> then I might as well run "groovyconsole" from the command line w/o maven.
> I've worked on the exec maven plugin which pulls in the artifacts to run code
> and surely GMaven can/should be doing this.
--
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
