[ http://jira.codehaus.org/browse/SCM-245?page=comments#action_81710 ] Bugittaa Pahasti commented on SCM-245: --------------------------------------
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: http://jira.codehaus.org/browse/SCM-245 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-perforce > Affects Versions: 1.0-beta-3 > Environment: WinXP with Cygwin, Perforce 2006.1 > Reporter: Bugittaa Pahasti > > 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 is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
