[
https://issues.apache.org/jira/browse/MNG-5440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MNG-5440.
-------------------------------
Resolution: Fixed
Assignee: Robert Scholte
Fix Version/s: (was: Issues to be reviewed for 4.x)
3.3.9
org.eclipse.sisu.inject-0.3.2 and org.eclipse.sisu.plexus-0.3.2 are part of
Maven 3.3.9 distribution, so should be fixed there.
> default-value on mojo parameter of type collection or array effectively make
> parameter read-only
> ------------------------------------------------------------------------------------------------
>
> Key: MNG-5440
> URL: https://issues.apache.org/jira/browse/MNG-5440
> Project: Maven
> Issue Type: Bug
> Reporter: Jan Sievers
> Assignee: Robert Scholte
> Fix For: 3.3.9
>
> Attachments: mojoParamsBug.zip
>
>
> If you use default-value on collection or array mojo parameters like
> {code:java}
> /**
> * @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
> {noformat}[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>{noformat}
> will not be aplied correctly:
> {noformat}[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]{noformat}
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)
