[
http://jira.codehaus.org/browse/MGROOVY-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon closed MGROOVY-105.
--------------------------------
Resolution: Fixed
I've added settings and session to the execute mojo's default namespace.
> Expose ExecuteMojo in script's execution context
> ------------------------------------------------
>
> Key: MGROOVY-105
> URL: http://jira.codehaus.org/browse/MGROOVY-105
> Project: Maven 2.x Groovy Integration
> Issue Type: Improvement
> Components: execute
> Affects Versions: 1.0-beta-3
> Reporter: Andrew Perepelytsya
> Assignee: Jason Dillon
> Fix For: 1.0-beta-4
>
>
> I'm facing a big problem - need to determine the path to the m2 repo used at
> runtime (e.g. get an artifact and scan it's file path). However, there's
> nothing like that accessible in the ExecuteMojo. I think adding the ['mojo',
> this] map would help, executed scripts could then peek into maven api.
--
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
