[
https://issues.apache.org/jira/browse/SCM-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17964500#comment-17964500
]
Olivier Lamy commented on SCM-329:
----------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-scm#543|https://github.com/apache/maven-scm/issues/543].
> Perforce where support edge case broken
> ---------------------------------------
>
> Key: SCM-329
> URL: https://issues.apache.org/jira/browse/SCM-329
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-scm-provider-perforce
> Affects Versions: 1.0-rc1
> Reporter: Mike Perham
> Assignee: Patrick Schneider
> Priority: Major
>
> It looks like there is a case where we are handed the full path rather than a
> relative path (in cases where the parent project is a peer to the child
> project on the filesystem). The fallback to p4 where needs to handle this
> case.
> {quote}
> [DEBUG] Sending changelist:
> Change: new
> Description:
> [maven-release-plugin] prepare for next development iteration
> Files:
> //depot/external/wicket-1.2.x/wicket-parent/pom.xml
>
> //depot/external/wicket-1.2.x/wicket-parent/C:/src/private/depot/external/wicket-1.2.x/wicket/pom.xml
>
> //depot/external/wicket-1.2.x/wicket-parent/C:/src/private/depot/external/wicket-1.2.x/wicket-extensions/pom.xml
> {quote}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
