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

Robert Scholte closed MRELEASE-997.
-----------------------------------
       Resolution: Fixed
         Assignee: Robert Scholte
    Fix Version/s: 3.0.0

For MRELEASE-993 the scm dependencies will be upgraded to 1.9.6 (not yet 
released)

> Unable to release:perform on windows if a file name contains spaces on windows
> ------------------------------------------------------------------------------
>
>                 Key: MRELEASE-997
>                 URL: https://issues.apache.org/jira/browse/MRELEASE-997
>             Project: Maven Release Plugin
>          Issue Type: Bug
>    Affects Versions: 2.5.3
>            Reporter: Juan Pablo Santos Rodríguez
>            Assignee: Robert Scholte
>            Priority: Major
>             Fix For: 3.0.0
>
>
> Using the 2.5.3 version of the release plugin, on a Windows 10 machine, to 
> generate the vote artifacts for the upcoming JSPWiki 2.10.3, I stumbled upon 
> the following error message while doing an {{mvn release:perform}}:
> {code}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-release-plugin:2.5.3:prepare (default-cli) on 
> project jspwiki-builder: An error occurred during the status check process: 
> Exception while executing SCM command.: Error while executing command. Error 
> inside systemOut parser: Illegal character in path at index 0: 
> "jspwiki-war/src/main/styles/haddock/fontjspwiki/FontJspwiki/Read%20Me.txt"
> {code}
> which resulted on being unable to prepare the release.
> Seems that this is caused by the underlying maven-scm-* artifacts' versions, 
> which seem to have caused this issue on other places too (f.ex.: 
> [https://issues.jenkins-ci.org/browse/JENKINS-24686]). This behaviour appears 
> to be caused by https://issues.apache.org/jira/browse/SCM-772, but that's 
> just an impression.
> The fix would be to simply bump {{scmVersion}} property from 1.9.4 to 1.9.5 
> on [https://svn.apache.org/viewvc/maven/release/trunk/pom.xml?view=markup#l88]
> Steps to reproduce:
> {{mvn release:prepare -DdryRun -DautoVersionSubmodules=true}} on 
> [https://github.com/apache/jspwiki/commit/0f38188a1c49fbefa957e7486a0ead943b8642d8]
> Workaround: declare 1.9.5 versions of maven-scm-* artifacts as 
> maven-release-plugin dependencies (as done on the aforementioned Jenkins 
> issue and at 
> [https://github.com/apache/jspwiki/commit/339d66c349ee0234c6e903b81a6af8d9eae842b5):]
> {code:xml}
>   <plugin>
>     <artifactId>maven-release-plugin</artifactId>
>     <version>2.5.3</version>
>     <dependencies>
>       <dependency>
>         <groupId>org.apache.maven.scm</groupId>
>         <artifactId>maven-scm-api</artifactId>
>         <version>1.9.5</version>
>       </dependency>
>       <dependency>
>         <groupId>org.apache.maven.scm</groupId>
>         <artifactId>maven-scm-providers-standard</artifactId>
>         <version>1.9.5</version>
>         <type>pom</type>
>         <scope>runtime</scope>
>       </dependency>
>     </dependencies>
>   </plugin>
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to