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 2007/07/10 22:03:13 UTC

[jira] Created: (SCM-329) Perforce where support edge case broken

Perforce where support edge case broken
---------------------------------------

                 Key: SCM-329
                 URL: http://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


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

        

[jira] Commented: (SCM-329) Perforce where support edge case broken

Posted by "Sam Beran (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/SCM-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=196316#action_196316 ] 

Sam Beran commented on SCM-329:
-------------------------------

Is this being worked on? I'm running head on into this issue and I'd be willing to take a look.



> Perforce where support edge case broken
> ---------------------------------------
>
>                 Key: SCM-329
>                 URL: http://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 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

        

[jira] Commented: (SCM-329) Perforce where support edge case broken

Posted by "Patrick Schneider (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/SCM-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=196501#action_196501 ] 

Patrick Schneider commented on SCM-329:
---------------------------------------

Not actively.  If you want to have a look, go for it.  I may have some time soon though.

> Perforce where support edge case broken
> ---------------------------------------
>
>                 Key: SCM-329
>                 URL: http://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 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