Maven 2 & 3

ciManagement from parent is not merging with children

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 2.0.4
  • Fix Version/s: 3.2
  • Component/s: Inheritance and Interpolation
  • Labels:
    None
  • Environment:
    linux jdk1.5.0_10 amd64
  • Complexity:
    Intermediate
  • Number of attachments :
    0

Description

If I define the following in my parent pom:

<ciManagement>
  <system>continuum</system>
  <url>http://blah</url>
</ciManagement>

and then in the child pom I have the following:

<ciManagement>
  <notifiers>
    <notifier>
      <type>mail</type>
      <configuration>
        <address>blah</address>
      </configuration>
    </notifier>
  </notifiers>
</ciManagement>

The ciManagement for the effective pom lacks the system and url properties from the parent pom. Seems like it should be merging them but isn't. This would helpful for reducing code duplication.

Issue Links

is duplicated by

Bug - A problem which impairs or prevents the functions of the product. MNG-5052 ciManagement configuration ignore combine.children

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.
relates to

Bug - A problem which impairs or prevents the functions of the product. MNG-3124 Inherit mailing lists from parent POM

  • Major - Major loss of function.
  • Open - The issue is open and ready for the assignee to start work on it.

Bug - A problem which impairs or prevents the functions of the product. MNG-3845 [regression] Unintended inheritance of parent elements overriden by children

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Paul Benedict added a comment - - edited

This would greatly help when submodules are ran by different developers. The software engineers can be placed in the parent POM, and additional developers notified via the children POM. In the company I work for, we aren't allowed to have custom mailing lists – so we have to list people (i.e., developers) individually in the POM. A pain, yes, but if this element was inheritable, it would be easier to deal with our constraint.

Show
Paul Benedict added a comment - - edited This would greatly help when submodules are ran by different developers. The software engineers can be placed in the parent POM, and additional developers notified via the children POM. In the company I work for, we aren't allowed to have custom mailing lists – so we have to list people (i.e., developers) individually in the POM. A pain, yes, but if this element was inheritable, it would be easier to deal with our constraint.
Hide
Permalink
Brett Porter added a comment -

this is currently by design - will need to review it in light of a model change

Show
Brett Porter added a comment - this is currently by design - will need to review it in light of a model change
Hide
Permalink
Brett Porter added a comment -

need to review the role of these elements in a POM review. They might be better just being general "configuration" across a set of plugins

Show
Brett Porter added a comment - need to review the role of these elements in a POM review. They might be better just being general "configuration" across a set of plugins
Hide
Permalink
Herve Boutemy added a comment -

MNG-3124 is exactly the same expectations and limits for mailing lists

Show
Herve Boutemy added a comment - MNG-3124 is exactly the same expectations and limits for mailing lists

People

  • Assignee:
    Unassigned
    Reporter:
    Kelly Davis
Vote (6)
Watch (4)

Dates

  • Created:
    Updated: