[ 
https://jira.codehaus.org/browse/MRELEASE-577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=296187#comment-296187
 ] 

Joseph Walton commented on MRELEASE-577:
----------------------------------------

This change seems to publish the passwords from a private settings.xml into a 
world-readable file in /tmp during a build.
                
> release:prepare does not pass argument "--settings" with current settings.xml 
> to inner maven
> --------------------------------------------------------------------------------------------
>
>                 Key: MRELEASE-577
>                 URL: https://jira.codehaus.org/browse/MRELEASE-577
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>          Components: prepare
>    Affects Versions: 2.0-beta-9, 2.0
>            Reporter: Petr Kozelka
>            Assignee: Stephen Connolly
>            Priority: Critical
>              Labels: contributers-welcome
>             Fix For: 2.2.2
>
>
> The impact is that release:prepare tries to use $HOME/.m2/settings.xml 
> instead of the one supplied by --settings cmdline option, which leads to 
> unexpected behavior
> Of course if it does not exist, the inhouse repository is avoided and release 
> often fails due to a ResourceDoesNotExistException when an inhouse artifact 
> is requested by the pom.
> To reproduce this problem, just rename your ~/.m2/settings.xml to ~/.m2/s.xml 
> and run this:
> mvn --settings=$HOME/.m2/s.xml release:prepare .....

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to