Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Won't Fix
-
1.0-rc1
-
None
-
None
Description
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.
[DEBUG] Sending changelist:
Change: newDescription:
[maven-release-plugin] prepare for next development iterationFiles:
//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