You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Mike Perham (JIRA)" <ji...@codehaus.org> on 2006/12/02 08:18:41 UTC

[jira] Closed: (SCM-229) Add support for p4 where

     [ http://jira.codehaus.org/browse/SCM-229?page=all ]

Mike Perham closed SCM-229.
---------------------------

       Resolution: Fixed
    Fix Version/s: 1.0

Updated all usage of repo.getPath() to refer through the PerforceScmProvider.getRepoPath() method which uses p4 where to "fix up" any SCM URL path issues if possible.

> Add support for p4 where
> ------------------------
>
>                 Key: SCM-229
>                 URL: http://jira.codehaus.org/browse/SCM-229
>             Project: Maven SCM
>          Issue Type: Improvement
>          Components: maven-scm-provider-perforce
>    Affects Versions: 1.0-beta-3
>            Reporter: Mike Perham
>         Assigned To: Mike Perham
>             Fix For: 1.0
>
>
> A common cause of Perforce failures is due to an inherited SCM url containing the incorrect depot location (common when the child directory != child artifactId).   We need to verify the depot location exists using 'p4 where'.

-- 
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