[MNG-5474] combine.children="merge" has reversed ordering of combine.children="append"

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 3.0.5
• Fix Version/s: 4.x / Backlog
• Component/s: POM
• Assignee: Guillaume Nodet
• Reporter: Tobias Oberlies
• Created: 03/May/13 07:37
• Updated: 10/Jan/24 16:43

Description

I have a configuration parameter that has a list of child elements (which themselves contain configuration elements). The child elements have distinct names, but their order matters. They each denote a pre-condition, and I want to be able to specify which one wins in case multiple pre-conditions apply.

Obviously, I want more specific configuration (e.g. execution level > plugin level) to win. As a plugin, I only get the merged configuration as list (using the parameter type PlexusConfiguration). So to achieve the desired precedence, I need to rely on the order of the child elements.

I was surprised to see that combine.children="merge" and combine.children="append" give opposite results. For the former, more specific configuration is a the top whereas for the latter, the more specific configuration is at the end of the list.

Example:

<configuration>
  <myParam combine.children="append">
    <parentMgtConfig>...</parentMgtConfig>
    <parentConfig>...</parentConfig>
    <pluginConfig>...</pluginConfig>
    <execConfig>...</execConfig>
  </myParam>
</configuration>

<configuration>
  <myParam combine.children="merge">
    <execConfig>...</execConfig>
    <pluginConfig>...</pluginConfig>
    <parentConfig>...</parentConfig>
    <parentMgtConfig>...</parentMgtConfig>
  </myParam>
</configuration>

I think that combine.children="merge" should also be in parent-first order.

Issue Links

• relates to: MJAR-172 Manifest entries are in wrong (visual) order