[ 
https://jira.codehaus.org/browse/SCM-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Osipov closed SCM-329.
------------------------------

    Resolution: Won't Fix

Please refer to 
https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014
 if you're wondering why this issue was closed out.

Assignee, if you think you can fix this bug anytime soon, please reopen and 
proceed appropriately.

> Perforce where support edge case broken
> ---------------------------------------
>
>                 Key: SCM-329
>                 URL: https://jira.codehaus.org/browse/SCM-329
>             Project: Maven SCM
>          Issue Type: Bug
>          Components: maven-scm-provider-perforce
>    Affects Versions: 1.0-rc1
>            Reporter: Mike Perham
>            Assignee: Patrick Schneider
>
> 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
(v6.1.6#6162)

Reply via email to