[ 
https://issues.apache.org/jira/browse/SUREFIRE-1047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15922895#comment-15922895
 ] 

Konrad Windszus commented on SUREFIRE-1047:
-------------------------------------------

I don't really see the need for this, as for all plugin parameters the 
properties are evaluated only directly before the mojo is being called in 
{{DefaultMavenPluginManager.getConfiguredMojo(...)}} 
(https://github.com/apache/maven/blob/master/maven-core/src/main/java/org/apache/maven/plugin/internal/DefaultMavenPluginManager.java#L594).

> Add @{...} property evaluation for the argLine
> ----------------------------------------------
>
>                 Key: SUREFIRE-1047
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-1047
>             Project: Maven Surefire
>          Issue Type: Improvement
>          Components: Maven Surefire Plugin
>    Affects Versions: 2.16
>            Reporter: Henning Schmiedehausen
>            Assignee: Andreas Gudian
>             Fix For: 2.17
>
>
> Replaces expressions @{property-name} in the argLine with the corresponding 
> properties from the model. This allows late evaluation of property values 
> when the plugin is executed (as compared to evaluation when the pom is parsed 
> as is done with ${property-name} expressions).
> This allows other plugins to modify or set properties with the changes
> getting picked up by surefire.
> Please merge the pull request at 
> https://github.com/apache/maven-surefire/pull/30



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to