[
http://jira.codehaus.org/browse/MNG-3062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter updated MNG-3062:
------------------------------
Fix Version/s: 2.0.x
thinking about whether this is a good idea... it is probably not harmful, but
I'm not sure if it would also be a best practice not to use it.
What is the use case you have? If the executions are structured appropriately,
I would think the mojo just runs or not, and the configuration can be used to
alter behaviour.
> Allow access to mojoExecution from within plugin.
> -------------------------------------------------
>
> Key: MNG-3062
> URL: http://jira.codehaus.org/browse/MNG-3062
> Project: Maven 2
> Issue Type: Improvement
> Affects Versions: 2.0.6
> Reporter: Paul Gier
> Fix For: 2.0.x
>
> Attachments: PluginParameterExpressionEvaluator.patch
>
>
> I would like to be able to access the execution ID from within a plugin.
> This could be useful for example to run only certain executions. This could
> be done with a small change to the plugin expression evaluator.
> I created a patch that would give the plugin access to the current
> MojoExecution.
--
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
