[
https://issues.apache.org/jira/browse/SCM-229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17960858#comment-17960858
]
ASF GitHub Bot commented on SCM-229:
------------------------------------
jira-importer commented on issue #490:
URL: https://github.com/apache/maven-scm/issues/490#issuecomment-2964598657
**[Mike
Perham](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=mperham)**
commented
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: https://issues.apache.org/jira/browse/SCM-229
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Improvement
> Components: maven-scm-provider-perforce
> Affects Versions: 1.0-beta-3
> Reporter: Mike Perham
> Assignee: Mike Perham
> Priority: Major
> Fix For: 1.0-beta-4
>
>
> 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 was sent by Atlassian Jira
(v8.20.10#820010)
