[MNG-6596] maven should not make assumptions on the location of the parent pom

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Cannot Reproduce
• Affects Version/s: 3.5.4, 3.6.0
• Environment: linux maven 3.5.4 and 3.6.0
• Flags: Important
• Assignee: Unassigned
• Reporter: Pieter van den Hombergh
• Created: 20/Feb/19 11:04
• Updated: 27/May/19 19:26
• Resolved: 27/May/19 19:19

Description

the parent pom is currently the way to go to set configurations for multiple projects, even if these projects are not siblings.

Creating and deploying a parent pom to be shared in many projects should not force you to copy the parent pom around. Configurations should be dealt with in the same way: Don not repeat (as in copy and waste) yourselves.

Making NO assumption OR ignoring the (default)) parentPath when the assumption does not match would solve this issue.

The problem is even more annoying when maven reacts differently to using the  same parent pom.

The parent pom in question can be found on github under statewalker sebipom