maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Perham (JIRA)" <>
Subject [jira] Closed: (SCM-245) scm:edit doesn't work with perforce as it refers the file without depot path
Date Sat, 02 Dec 2006 07:14:41 GMT
     [ ]

Mike Perham closed SCM-245.

    Resolution: Cannot Reproduce

I'm not sure the edit command works the way you think it works.  The edit command does not
check out anything from the depot, so using a full depot location doesn't really make much
sense.  Your example makes it obvious that your clientspec does not map the file so there's
no reason to think this should work in the first place.  When the file is properly mapped
in the clientspec, the edit command works as designed.

> scm:edit doesn't work with perforce as it refers the file without depot path
> ----------------------------------------------------------------------------
>                 Key: SCM-245
>                 URL:
>             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:
For more information on JIRA, see:


View raw message