[
https://issues.apache.org/jira/browse/SCM-340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17964517#comment-17964517
]
Olivier Lamy commented on SCM-340:
----------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-scm#568|https://github.com/apache/maven-scm/issues/568].
> VSS Provider fails during check out when project path contains spaces
> ---------------------------------------------------------------------
>
> Key: SCM-340
> URL: https://issues.apache.org/jira/browse/SCM-340
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-scm-provider-vss
> Affects Versions: 1.0
> Environment: Windows XP, JRE 1.4.2
> Reporter: Allan Lang
> Assignee: Olivier Lamy
> Priority: Major
>
> VSS Provider fails during check out if project path contains a space. For
> example, using the following SCM URL:
> {{scm:vss|guest@\\someserver\somefolder|/top path}}
> This results in the following output:
> {code}
> Executing: "c:\program files\microsoft visual studio\vss\win32\ss" Get
> "$/project root" -Yguest -R -I- -GWR
> Working directory: c:\temp\fiddler
> Provider message:
> The vss command failed.
> Command output:
> 'c:\program' is not recognized as an internal or external command,
> operable program or batch file.
> java.lang.Exception: Command failed.The vss command failed.
> at com.goongo.vssscmtest.MyTest.checkResult(MyTest.java:125)
> at com.goongo.vssscmtest.MyTest.checkOut(MyTest.java:75)
> at com.goongo.vssscmtest.MyTest.main(MyTest.java:29)
> Exception in thread "main"
> {code}
> This appears to be due to a bug in plexus-utils-1.1. If this dependency is
> updated to v1.4 (or later) this error is fixed.
> Therefore, resolution is to update dependency in pom.xml of maven-scm project.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
