[
https://issues.apache.org/jira/browse/MNG-2751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16737274#comment-16737274
]
Wojtek commented on MNG-2751:
-----------------------------
Just to give it a nudge - I just run into this issue. Most of the time
configuration is merged (or it's possibility to specify inheritance policy:
merge/replace/etc).
Happens in: `Apache Maven 3.6.0 (97c98ec64a1fdfee7767ce5ffb20918da4f719f3;
2018-10-24T15:41:47-03:00)`
> Resource inheritance isn't additive
> -----------------------------------
>
> Key: MNG-2751
> URL: https://issues.apache.org/jira/browse/MNG-2751
> Project: Maven
> Issue Type: Bug
> Components: Inheritance and Interpolation
> Affects Versions: 2.0.4
> Environment: All
> Reporter: Jason Melnick
> Priority: Major
>
> 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 was sent by Atlassian JIRA
(v7.6.3#76005)
