You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Pat Leamon (JIRA)" <ji...@codehaus.org> on 2009/12/15 12:35:55 UTC
[jira] Created: (MNG-4493) Plugin parameters are no longer expanded
from properties CDATA sections
Plugin parameters are no longer expanded from properties CDATA sections
-----------------------------------------------------------------------
Key: MNG-4493
URL: http://jira.codehaus.org/browse/MNG-4493
Project: Maven 2 & 3
Issue Type: Bug
Affects Versions: 2.2.1
Reporter: Pat Leamon
Priority: Minor
In version 2.0.9 we used properties to configure a parameter (of type List) for a plugin.
i.e.
<properties>
<databaselist>
<![CDATA[
<databaseToMigrate>
<connectionUsername>userA</connectionUsername>
<connectionPassword>passwordA</connectionPassword>
</databaseToMigrate>
<databaseToMigrate>
<connectionUsername>userB</connectionUsername>
<connectionPassword>passwordB</connectionPassword>
</databaseToMigrate>
]]>
</databaselist>
</properties>
...
<plugin>
...
<configuration>
<databases>${databaselist}</databases>
...
</configuration>
</plugin>
...
In 2.2.1 this no longer works. Maven complains that type String doesn't match type List. I guess it is preserving the CDATA section as a String.
Is this intended behaviour now? Is there any way that we could keep xml fragments in a property and then use them in parameters?
I can workaround this by redefining the plugin config in each pom, it's just less elegant.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-4493) Plugin parameters are no longer expanded
from properties CDATA sections
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann closed MNG-4493.
----------------------------------
Resolution: Not A Bug
Fix Version/s: (was: Issues to be reviewed for 3.x)
Assignee: Benjamin Bentmann
The {{properties}} element basically models {{java.util.Properties}} and is meant to carry only plain strings and as a consequence any expression referring to those properties yields a just a string.
> Plugin parameters are no longer expanded from properties CDATA sections
> -----------------------------------------------------------------------
>
> Key: MNG-4493
> URL: http://jira.codehaus.org/browse/MNG-4493
> Project: Maven 2 & 3
> Issue Type: Bug
> Affects Versions: 2.2.1
> Reporter: Pat Leamon
> Assignee: Benjamin Bentmann
> Priority: Minor
>
> In version 2.0.9 we used properties to configure a parameter (of type List) for a plugin.
> i.e.
> <properties>
> <databaselist>
> <![CDATA[
> <databaseToMigrate>
> <connectionUsername>userA</connectionUsername>
> <connectionPassword>passwordA</connectionPassword>
> </databaseToMigrate>
> <databaseToMigrate>
> <connectionUsername>userB</connectionUsername>
> <connectionPassword>passwordB</connectionPassword>
> </databaseToMigrate>
> ]]>
> </databaselist>
> </properties>
> ...
> <plugin>
> ...
> <configuration>
> <databases>${databaselist}</databases>
> ...
> </configuration>
> </plugin>
> ...
> In 2.2.1 this no longer works. Maven complains that type String doesn't match type List. I guess it is preserving the CDATA section as a String.
> Is this intended behaviour now? Is there any way that we could keep xml fragments in a property and then use them in parameters?
> I can workaround this by redefining the plugin config in each pom, it's just less elegant.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira