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

Thomas Kunkel updated SCM-859:
------------------------------
    Labels:   (was: easyfix)

> SVN Update doesn't work when directory contains "@"
> ---------------------------------------------------
>
>                 Key: SCM-859
>                 URL: https://issues.apache.org/jira/browse/SCM-859
>             Project: Maven SCM
>          Issue Type: Bug
>          Components: maven-scm-provider-svn
>    Affects Versions: 1.9.5
>            Reporter: Thomas Kunkel
>            Priority: Minor
>
> scm:update with the svn provider doesn't work when the working directory 
> contains an "@"
> Following the error message when the folder itself has an "@" sign
> {code:java}
> [INFO] Scanning for projects...
> [INFO]
> [INFO] 
> ------------------------------------------------------------------------
> [INFO] Building svntest 0.0.1-SNAPSHOT
> [INFO] 
> ------------------------------------------------------------------------
> [INFO]
> [INFO] --- maven-scm-plugin:1.9.5:update (default-cli) @ svntest ---
> [INFO] Executing: cmd.exe /X /C "svn --non-interactive update 
> C:\SVNTest\failingTest@"
> [INFO] Working directory: C:\SVNTest\failingTest@
> [ERROR] Provider message:
> [ERROR] The svn command failed.
> [ERROR] Command output:
> [ERROR] svn: E155007: None of the targets are working copies
> [INFO] 
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] 
> ------------------------------------------------------------------------
> [INFO] Total time: 1.357 s
> [INFO] Finished at: 2018-02-07T12:35:08+01:00
> [INFO] Final Memory: 11M/155M
> [INFO] 
> ------------------------------------------------------------------------
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-scm-plugin:1.9.5:update (default-cli) on 
> project svntest: Command failed.The svn command failed. -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please 
> read the following articles:
> [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException{code}
> Following the error when the "@" sign is in an parent folder name
> {code:java}
> [INFO] Scanning for projects...
> [INFO]
> [INFO] 
> ------------------------------------------------------------------------
> [INFO] Building svntest 0.0.1-SNAPSHOT
> [INFO] 
> ------------------------------------------------------------------------
> [INFO]
> [INFO] --- maven-scm-plugin:1.9.5:update (default-cli) @ svntest ---
> [INFO] Executing: cmd.exe /X /C "svn --non-interactive update 
> C:\SVNTest\failingTest@\Subfolderfail"
> [INFO] Working directory: C:\SVNTest\failingTest@\Subfolderfail
> [ERROR] Provider message:
> [ERROR] The svn command failed.
> [ERROR] Command output:
> [ERROR] svn: E200009: 'C:********@\Subfolderfail': a peg revision is not 
> allowed here
> [INFO] 
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] 
> ------------------------------------------------------------------------
> [INFO] Total time: 1.248 s
> [INFO] Finished at: 2018-02-07T12:35:33+01:00
> [INFO] Final Memory: 11M/155M
> [INFO] 
> ------------------------------------------------------------------------
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-scm-plugin:1.9.5:update (default-cli) on 
> project svntest: Command failed.The svn command failed. -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please 
> read the following articles:
> [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException{code}
> This error can be fixed by appending an additional "@" after the path in the 
> command.



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

Reply via email to