[MSHADE-124] Need better plan for getting dependency-reduced-pom.xml out of basedir

• Type: Bug
• Status: Reopened
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.7.1
• Assignee: Unassigned
• Reporter: Benson Margulies
• Created: 27/Jun/12 06:40
• Updated: 06/Feb/23 07:37

Description

MSHADE-123 reported that putting the d-r-p into some location other
than 'basedir' causes 'basedir' to follow it around, which can break builds.

This is hard to fix, given the core maven definition of basedir as 'the dir containing the pom' with no option to change it.

Issue Links

• blocks: MSHADE-160 change default location of dependency-reduced-pom.xml
• is related to: MSHADE-329 Concurrent writes of dependency-reduced-pom.xml adds same exclusion ad infinitum
• is related to: MRELEASE-878 Exclude generated dependency-reduced-pom.xml and flattened-pom.xml
• is related to: MSHADE-145 Site not generated correctly when overriding dependencyReducedPomLocation with relocation
• is related to: MSHADE-123 1.7 Causes failures in other plugins make "basedir" point to the build dir
• links to: GitHub Pull Request #128