[ 
https://jira.codehaus.org/browse/MRELEASE-785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rob Elliot updated MRELEASE-785:
--------------------------------

    Attachment: MRELEASE-785-maven-release.patch
                MRELEASE-785-maven-release-2.3.2.patch

Plexus Utils 3.0.4 has been released, which fixes this issue.  These patches 
upgrade to this version, and are valid for trunk & the 2.3.2 tag respectively.
                
> Arguments containing spaces and quotes cause the forked maven process to fail
> -----------------------------------------------------------------------------
>
>                 Key: MRELEASE-785
>                 URL: https://jira.codehaus.org/browse/MRELEASE-785
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>          Components: prepare
>    Affects Versions: 2.3.2
>         Environment: *nix
>            Reporter: Rob Elliot
>         Attachments: MRELEASE-785-maven-release-2.3.2.patch, 
> MRELEASE-785-maven-release.patch
>
>
> The following config:
> {code:xml}
> <plugin>
>             <artifactId>maven-release-plugin</artifactId>
>             <configuration>
>               <mavenExecutorId>forked-path</mavenExecutorId>
>               <useReleaseProfile>false</useReleaseProfile>
>               <arguments>-Dgpg.passphrase="a phrase 'containing' quotes and 
> spaces"</arguments>
>             </configuration>
>           </plugin>
> {code}
> causes the forked clean verify to fail.  This is preventing me using my gpg 
> key as part of an automated release process.
> This is due to a bug in Plexus Utils which I have raised as issue 152 
> PLXUTILS-152, and for which I have raised a pull request here: 
> https://github.com/sonatype/plexus-utils/pull/5.  I am raising an issue on 
> the release plugin as when/if a fixed version of plexus utils is released the 
> maven release plugin will need to upgrade to this new version to benefit.

--
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