[ http://jira.codehaus.org/browse/MNG-2751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=224758#action_224758 ]
Jason Shao commented on MNG-2751: --------------------------------- Still the case as of 2.2.1 - though I can't change the Affect Versions. If this is not going to be addressed, I'd like to get the documentation fixed, from http://maven.apache.org/guides/introduction/introduction-to-the-pom.html > Resource inheritance isn't additive > ----------------------------------- > > Key: MNG-2751 > URL: http://jira.codehaus.org/browse/MNG-2751 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Inheritance and Interpolation > Affects Versions: 2.0.4 > Environment: All > Reporter: Jason Melnick > Fix For: Issues to be reviewed for 3.x > > > I have an inheritance model as such: > Parent_POM (General dependencyManagement, pluginManagement, etc) > |-->Base_POM (global dependency inclusion, default goal, default plugins, etc) > |-->Artifact_POM (declares specific artifact type functionality, > resources, profiles, etc) > |-->Project_POM (project specific dependencies, resources, etc) > I am attempting to create an hierarchy that will enable a new project to get > up and running with very little modification. The issue I am having is if > build.resources are declared in the Project_POM they are wiping the > Artifact_POM's declarations. > I think that resources should always be additive. If nothing else add an > <inherited> tag a la the plugin element's <inherited> tag. In lieu of that > perhaps a resourceManagement section that exposes resource id's that could be > selectively added by the child... -- 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