[
https://issues.apache.org/jira/browse/SCM-269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17959864#comment-17959864
]
ASF GitHub Bot commented on SCM-269:
------------------------------------
jira-importer opened a new issue, #260:
URL: https://github.com/apache/maven-scm/issues/260
**[David
Jackman](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=djackman)**
opened
**[SCM-269](https://issues.apache.org/jira/browse/SCM-269?redirect=false)** and
commented
Create a view of a Maven project in Perforce in a local directory whose path
contains a space. Perform some SCM goal (I was trying to scm:update). It
won't work. The error message is very cryptic ("Unable to sync. Are you
logged in?"). From the looks of it, the client command (which is run just
before the sync command) has problems, but these problems aren't reported. I
think the main problem is the fact that the local path is used in the client
name, and client names can't contain spaces. Other elements of the client
(root and view) also will contain spaces, but I don't know if Perforce has a
problem with these.
---
**Affects:** 1.0-beta-4
1 votes, 2 watchers
> Perforce support doesn't work when there's a space in the local path
> --------------------------------------------------------------------
>
> Key: SCM-269
> URL: https://issues.apache.org/jira/browse/SCM-269
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-scm-provider-perforce
> Affects Versions: 1.0-beta-4
> Reporter: David Jackman
> Assignee: Mike Perham
> Priority: Major
>
> Create a view of a Maven project in Perforce in a local directory whose path
> contains a space. Perform some SCM goal (I was trying to scm:update). It
> won't work. The error message is very cryptic ("Unable to sync. Are you
> logged in?"). From the looks of it, the client command (which is run just
> before the sync command) has problems, but these problems aren't reported. I
> think the main problem is the fact that the local path is used in the client
> name, and client names can't contain spaces. Other elements of the client
> (root and view) also will contain spaces, but I don't know if Perforce has a
> problem with these.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)