maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "chris damour (JIRA)" <>
Subject [jira] [Commented] (MNG-2751) Resource inheritance isn't additive
Date Thu, 02 Nov 2017 19:43:00 GMT


chris damour commented on MNG-2751:

spring boot is a great example to this, the parent has 


and any boot app using it can't modify this without recreating all functionality

> Resource inheritance isn't additive
> -----------------------------------
>                 Key: MNG-2751
>                 URL:
>             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,
>           |-->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

View raw message