You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Mickael Istria (JIRA)" <ji...@codehaus.org> on 2013/10/14 08:41:52 UTC

[jira] (MNG-5347) Support expressions for plugin parameters

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

Mickael Istria commented on MNG-5347:
-------------------------------------

You're right, this is much more about supporting expression languages (ideally Groovy) in ${...} blocks.
It was discussed some time ago: http://maven.40175.n5.nabble.com/Discuss-Using-Expression-Language-in-POM-td3228668.html and the conclusion was that introducing script would be against the current descriptive & XML only approach. Despite of the output of this discussion, it is clear the allowing expression language in ${...} blocks would be a pragmatic and helpful improvement.
                
> Support expressions for plugin parameters
> -----------------------------------------
>
>                 Key: MNG-5347
>                 URL: https://jira.codehaus.org/browse/MNG-5347
>             Project: Maven 2 & 3
>          Issue Type: Wish
>          Components: General
>    Affects Versions: 3.0.4
>         Environment: mistria@mistria--rh:~$ mvn -version
> Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100)
> Maven home: /home/mistria/apps/apache-maven-3.0.4
> Java version: 1.6.0_24, vendor: Sun Microsystems Inc.
> Java home: /usr/lib/jvm/java-6-openjdk-amd64/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "3.2.0-30-generic", arch: "amd64", family: "unix"
>            Reporter: Mickael Istria
>
> Use-case:
> I want to give as input of my surefire-plugin
> {code}
> <configuration>
>     <skip>${skipTests} || ${skipDownloadRuntimes}</skip>
> <configuration>
> {code}
> This won't work because the expressions are not evaluated. Boolean arguments in plugin are set to something like Boolean.parseBoolean, which is quite limited.
> Instead, we could think of introducing an expression language, such as Groovy, that would allow expressions as parameters for plugins.
> Then let's say skipTests=false and skipDownloadRuntimes=true, Maven would first replace "${skipTests} || ${skipDownloadRuntimes}" by "false || true" and then this evaluator would evaluate that to "false", and skip will receive the value "false".
> This would for sure make maven less verbose in some cases.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira