You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org> on 2009/10/11 13:15:49 UTC
[jira] Moved: (MNGSITE-99) POM reference not discuss configuration
merging
[ http://jira.codehaus.org/browse/MNGSITE-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann moved MNG-4389 to MNGSITE-99:
-----------------------------------------------
Complexity: (was: Intermediate)
Component/s: (was: Documentation: General)
Affects Version/s: (was: Documentation Deficit)
Key: MNGSITE-99 (was: MNG-4389)
Project: Maven 2 Project Web Site (was: Maven 2)
> POM reference not discuss configuration merging
> -----------------------------------------------
>
> Key: MNGSITE-99
> URL: http://jira.codehaus.org/browse/MNGSITE-99
> Project: Maven 2 Project Web Site
> Issue Type: Improvement
> Reporter: Paul Benedict
> Priority: Minor
>
> I was reading this:
> http://www.sonatype.com/people/2007/06/how-to-merge-sub-items-from-parent-pom-to-child-pom-in-a-maven-plugin-configuration-2/
> Using Maven 2.2.1, is it still supported? Is there a better option? It's tough to tell since the property is not mentioned by any docs.
> My recommendation is to add the "combine.children" attribute to the POM reference (/pom.html) with possible values and behavior.
--
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