You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2005/11/30 12:40:06 UTC
[jira] Closed: (MNG-1715) Absolute paths in exported-pom.xml
[ http://jira.codehaus.org/browse/MNG-1715?page=all ]
Brett Porter closed MNG-1715:
-----------------------------
Assign To: Brett Porter
Resolution: Duplicate
> Absolute paths in exported-pom.xml
> ----------------------------------
>
> Key: MNG-1715
> URL: http://jira.codehaus.org/browse/MNG-1715
> Project: Maven 2
> Type: Bug
> Components: Plugins and Lifecycle
> Versions: 2.0
> Reporter: Yann Le Du
> Assignee: Brett Porter
> Priority: Minor
>
>
> 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
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org