[
https://jira.codehaus.org/browse/MRELEASE-857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=336570#comment-336570
]
Robert Scholte commented on MRELEASE-857:
-----------------------------------------
Thanks for the explanation, it makes the usecase clear for me.
There's a trick for the arguments as well:
{code:xml}
<project>
<properties>
<arguments />
</properties>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-release-plugin</artifactId>
</plugin>
<configuration>
<arguments>-Dkey=value ${arguments}</arguments>
</configuration>
</plugins>
</build>
</project>
{code}
This way you can extend the arguments and have full control over the arguments
passed to the MavenInvoker.
I'd like to keep the direct executed environment separated from the invoked
environment, so no magic properties if it is not required.
> 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
