[
https://jira.codehaus.org/browse/MENFORCER-220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl-Heinz Marbaise closed MENFORCER-220.
-----------------------------------------
Resolution: Fixed
Assignee: Karl-Heinz Marbaise
Patch applied by Konrad Windszus in [r1649120|http://svn.apache.org/r1649120].
Thank you.
A slight change made to the patch:
Not using the following:
{code:java}
@Component( role = MojoExecution.class )
protected MojoExecution mojoExecution;
{code}
using the following:
{code:java}
@Parameter( defaultValue = "${mojoExecution}", readonly = true, required = true
)
protected MojoExecution mojoExecution;
{code}
> Make real MojoExecution available through the EnforcerExpressionEvaluator
> -------------------------------------------------------------------------
>
> Key: MENFORCER-220
> URL: https://jira.codehaus.org/browse/MENFORCER-220
> Project: Maven Enforcer Plugin
> Issue Type: Improvement
> Affects Versions: 1.3.1
> Reporter: Konrad Windszus
> Assignee: Karl-Heinz Marbaise
> Fix For: 1.4
>
>
> Currently through the EnforcerExpressionEvaluator only the session and the
> project are available. The MojoExecution (incl. the lifecyclePhase) is just
> an empty default
> (https://github.com/apache/maven-enforcer/blob/trunk/enforcer-rules/src/main/java/org/apache/maven/plugins/enforcer/EnforcerExpressionEvaluator.java#L49).
> Instead the real MojoExecution of the maven-enforcer-plugin should be made
> available through the evaluator.
> My use case is that I want to check within a custom rule in which lifecycle
> the rule was executed. This is currently not possible since the livecycle
> phase is always null.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
