You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Karl-Heinz Marbaise (JIRA)" <ji...@codehaus.org> on 2015/01/02 21:58:10 UTC
[jira] (MENFORCER-220) Make real MojoExecution available through
the EnforcerExpressionEvaluator
[ https://jira.codehaus.org/browse/MENFORCER-220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Karl-Heinz Marbaise updated MENFORCER-220:
------------------------------------------
Fix Version/s: (was: waiting-for-feedback)
1.4
> 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
> 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)