Juan Pablo Santos Rodríguez created MRELEASE-997:

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

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

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

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 

Steps to reproduce:

{{mvn release:prepare -DdryRun -DautoVersionSubmodules=true}} on 

Workaround: declare 1.9.5 versions of maven-scm-* artifacts as 
maven-release-plugin dependencies (as done on the aforementioned Jenkins issue 
and at 

This message was sent by Atlassian JIRA

Reply via email to