You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jan Sievers (JIRA)" <ji...@codehaus.org> on 2013/02/25 15:57:52 UTC

[jira] (MNG-5440) default-value on mojo parameter of type collection or array effectively make parameter read-only

Jan Sievers created MNG-5440:
--------------------------------

             Summary: default-value on mojo parameter of type collection or array effectively make parameter read-only
                 Key: MNG-5440
                 URL: https://jira.codehaus.org/browse/MNG-5440
             Project: Maven 2 & 3
          Issue Type: Bug
            Reporter: Jan Sievers
         Attachments: mojoParamsBug.zip

If you use default-value on collection or array mojo parameters like

{code}
    /**
     * @parameter default-value="foo,bar"
     */
    private List<String> param1;
{code}

the default value will always win over pom.xml configuration.
See demo project attached.
Steps to reproduce:

1. {{mvn install}} on the demo project
2. {{mvn compile -f test-pom.xml -X -e}} on the demo project

you can see in the debug log that mojo configuration

[DEBUG] Configuration: <?xml version="1.0" encoding="UTF-8"?>
<configuration>
  <param1 default-value="foo,bar">
    <param1>non-default value1 param1</param1>
    <param1>non-default value2 param1</param1>
  </param1>
  <param2 default-value="baz">
    <param2>non-default value1 param2</param2>
    <param2>non-default value2 param2</param2>
  </param2>
</configuration>

will not be aplied correctly:

[DEBUG] Configuring mojo 'mojoParamsBug:mojoParamsBug:0.0.1-SNAPSHOT:demo' with basic configurator -->
[DEBUG]   (f) param1 = [foo, bar]
[DEBUG]   (f) param2 = [baz]
[DEBUG] -- end configuration --
[INFO] param1: [foo, bar]
[INFO] param2: [baz]


If default values for srrays/collection are not supported, this should fail the build in step 1. above.
If they are supported, the configurator should be fixed to actually allow configuring non-default values.


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