[MNG-1715] Absolute paths in exported-pom.xml

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Duplicate
• Affects Version/s: 2.0
• Component/s: Plugins and Lifecycle
• Assignee: Brett Porter
• Reporter: Yann Le Du
• Created: 30/Nov/05 04:38
• Updated: 06/Apr/15 00:05
• Resolved: 30/Nov/05 05:38

Description

The exported-pom.xml generated by the 'package' phase contains absolute paths in the <build> section - and also some relative ones, as <scriptSourceDirectory>. Is this behaviour on purpose ?

This exported-pom.xml is used for the 'deploy' phase - and also maybe for the maven-release-plugin. Although these absolute paths are not used when the deployed POM is used for a dependency, they :

• can be a security issue, as we don't want to show full information about our development environment
• are, unless I'm mistaken, useless information

Issue Links

• duplicates: MJAR-14 pom.xml information automatically included in META-INF during jar