[jira] [Commented] (MNG-2751) Resource inheritance isn't additive
[ https://issues.apache.org/jira/browse/MNG-2751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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 > tag a la the plugin element's 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)
[jira] [Commented] (MNG-2751) Resource inheritance isn't additive
[
https://issues.apache.org/jira/browse/MNG-2751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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
> tag a la the plugin element's 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)
[jira] [Commented] (MNG-2751) Resource inheritance isn't additive
[
https://issues.apache.org/jira/browse/MNG-2751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16236477#comment-16236477
]
chris damour commented on MNG-2751:
---
spring boot is a great example to this, the parent has
{code}
${basedir}/src/main/resources
true
**/application.yml
**/application.properties
${basedir}/src/main/resources
**/application.yml
**/application.properties
{code}
and any boot app using it can't modify this without recreating all functionality
> 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
> tag a la the plugin element's 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)
[jira] Commented: (MNG-2751) Resource inheritance isn't additive
[ https://jira.codehaus.org/browse/MNG-2751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=280347#comment-280347 ] daniel carter commented on MNG-2751: and an flag to allow merging, as happens for other pom elements. You should be able to specify resources parent=merge resourcedirectorysrc/main/licence/directory/resource /resources instead of this monstrosity - no wonder maven gets a reputation for verbosity! plugins plugin groupIdorg.codehaus.mojo/groupId artifactIdbuild-helper-maven-plugin/artifactId version1.7/version executions execution idadd-resource/id phasegenerate-resources/phase goals goaladd-resource/goal /goals configuration resources resourcedirectorysrc/main/licence/directory/resource /resources /configuration /execution /executions /plugin /plugins Resource inheritance isn't additive --- Key: MNG-2751 URL: https://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. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-2751) Resource inheritance isn't additive
[ http://jira.codehaus.org/browse/MNG-2751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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
