maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Slawomir Jaranowski (JIRA)" <j...@codehaus.org>
Subject [jira] (MRELEASE-857) release:perform does not pass argument "-Dsettings.security" to inner maven process
Date Sun, 01 Dec 2013 14:52:45 GMT

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

Slawomir Jaranowski commented on MRELEASE-857:
----------------------------------------------

Maybe system property "settings.security" is not good documented.

"settings.security" indicates location of master pasword file "settings-security.xml", but
option "-s" indicate where is standard maven settings.xml file. Option "-gs" is also not for
master pasword file.

It is mentioned in http://jira.codehaus.org/browse/MNG-4853 and also you can find it in source
code of plexus-sec-dispatcher https://github.com/sonatype/plexus-sec-dispatcher/blob/master/src/main/java/org/sonatype/plexus/components/sec/dispatcher/DefaultSecDispatcher.java

You can try: mvn -e -Dsettings.security=test -ep abc

I try use this property on CI system, when we have one CI for many teams and each team has
own settings.xml and settings-security.xml.

Using -Darguments some times is complicated when project has own configuration of maven-release-plugin
with custom arguments, for example you can read:
http://stackoverflow.com/questions/16005437/passing-arguments-to-maven-release-build

So -Darguments not working in such situations.

It will be nice if release plugin can understand this property. 
                
> release:perform does not pass argument "-Dsettings.security" to inner maven process
> -----------------------------------------------------------------------------------
>
>                 Key: MRELEASE-857
>                 URL: https://jira.codehaus.org/browse/MRELEASE-857
>             Project: Maven Release Plugin
>          Issue Type: Bug
>          Components: perform
>            Reporter: Slawomir Jaranowski
>
> When we run mvn release:perform with -Dsettings.security=custom-security.xml first step
use our custom security file, but inner process use standard location of master password file.
> This issue are more important after MRELEASE-766, because prepared settings.xml file
more often contains encrypted password.

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

Mime
View raw message