[
https://issues.apache.org/jira/browse/SCM-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17963132#comment-17963132
]
ASF GitHub Bot commented on SCM-245:
------------------------------------
jira-importer opened a new issue, #1022:
URL: https://github.com/apache/maven-scm/issues/1022
**[syvalta](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=syvalta)**
opened
**[SCM-245](https://issues.apache.org/jira/browse/SCM-245?redirect=false)** and
commented
Both of the commands fail to actually checkout the file for edit:
mvn scm:edit -Dincludes="pom.xml"
[DEBUG] Executing p4 edit pom.xml
mvn scm:edit -Dincludes="//depot/main/java/pom.xml"
[DEBUG] Executing p4 edit
The error is consumed and there's no indication of any error, even the
command fails. The command that would work would be "p4 edit
//depot/main/java/pom.xml". I suspect at least the former command is supposed
to work, but the provider fails to add the depot path to it.
If the command the plugin tries to use in run on the command line, it fails:
$ p4 edit pom.xml
Path 'xyz/main/java\pom.xml' is not under client's root '/rootpath'.
---
**Affects:** 1.0-beta-3
**Issue Links:**
- [SCM-209](https://issues.apache.org/jira/browse/SCM-209) Specifying
working directory for Runtime.exec() on linux has no effect
> scm:edit doesn't work with perforce as it refers the file without depot path
> ----------------------------------------------------------------------------
>
> Key: SCM-245
> URL: https://issues.apache.org/jira/browse/SCM-245
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-scm-provider-perforce
> Affects Versions: 1.0-beta-3
> Environment: WinXP with Cygwin, Perforce 2006.1
> Reporter: syvalta
> Priority: Major
>
> Both of the commands fail to actually checkout the file for edit:
> mvn scm:edit -Dincludes="pom.xml"
> [DEBUG] Executing p4 edit pom.xml
> mvn scm:edit -Dincludes="//depot/main/java/pom.xml"
> [DEBUG] Executing p4 edit
> The error is consumed and there's no indication of any error, even the
> command fails. The command that would work would be "p4 edit
> //depot/main/java/pom.xml". I suspect at least the former command is supposed
> to work, but the provider fails to add the depot path to it.
> If the command the plugin tries to use in run on the command line, it fails:
> $ p4 edit pom.xml
> Path 'xyz/main/java\pom.xml' is not under client's root '/rootpath'.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
