maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl-Heinz Marbaise (JIRA)" <j...@codehaus.org>
Subject [jira] (MENFORCER-220) Make real MojoExecution available through the EnforcerExpressionEvaluator
Date Fri, 02 Jan 2015 21:00:10 GMT

    [ https://jira.codehaus.org/browse/MENFORCER-220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=360568#comment-360568
] 

Karl-Heinz Marbaise commented on MENFORCER-220:
-----------------------------------------------

Ah..that enlighted me. Thanks.

> 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)

Mime
View raw message