[
https://issues.apache.org/jira/browse/SCM-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17963133#comment-17963133
]
ASF GitHub Bot commented on SCM-245:
------------------------------------
jira-importer commented on issue #1022:
URL: https://github.com/apache/maven-scm/issues/1022#issuecomment-2964639492
**[syvalta](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=syvalta)**
commented
Clientspec is set correctly, but actually the problem seems to be cygwin
related. Everything works fine when run from WinXP command prompt with both p4
or maven-scm, but it fails in both cases when run under cygwin.
So there are two issues:
- scm:edit doesn't work with cygwin
- scm:edit consumes errors, and reports "Build successful" even the command
failed. Not sure if this applies to other commands too.
> 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)
