[
https://issues.apache.org/jira/browse/MNG-2751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16298795#comment-16298795
]
Ohad Kravchick commented on MNG-2751:
-------------------------------------
My [private] projects has a similar need. I am using the jacoco code coverage
plugin (http://www.eclemma.org/jacoco/trunk/doc/maven.html) in a parent pom and
want to specify some default exclusions there (for example, {{**/Test*.java}}),
but to allow individual child project poms to *add* exclusions of their own.
> 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
>
> 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
(v6.4.14#64029)
