[
https://jira.codehaus.org/browse/MENFORCER-220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=359376#comment-359376
]
Konrad Windszus commented on MENFORCER-220:
-------------------------------------------
This should be fairly easy to accomplish by just injecting the MojoExecution
into {{AbstractEnforceMojo}}
(https://github.com/apache/maven-enforcer/blob/trunk/maven-enforcer-plugin/src/main/java/org/apache/maven/plugins/enforcer/AbstractEnforceMojo.java),
similar to {{MavenSession}} and {{MavenProject}} and then passing that to
{{EnforcerExpressionEvaluator}}
(https://github.com/apache/maven-enforcer/blob/trunk/enforcer-rules/src/main/java/org/apache/maven/plugins/enforcer/EnforcerExpressionEvaluator.java)
> Make real MojoExecution available through the EnforcerExpressionEvaluator
> -------------------------------------------------------------------------
>
> Key: MENFORCER-220
> URL: https://jira.codehaus.org/browse/MENFORCER-220
> Project: Maven Enforcer Plugin
> Issue Type: Bug
> Affects Versions: 1.3.1
> Reporter: Konrad Windszus
>
> 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)
