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 2006/03/28 00:10:44 UTC

[jira] Closed: (SCM-165) PerforceChangeLogCommand needs to use the same clientspec as the update command

     [ http://jira.codehaus.org/browse/SCM-165?page=all ]
     
Mike Perham closed SCM-165:
---------------------------

     Resolution: Fixed
    Fix Version: 1.0

> PerforceChangeLogCommand needs to use the same clientspec as the update command
> -------------------------------------------------------------------------------
>
>          Key: SCM-165
>          URL: http://jira.codehaus.org/browse/SCM-165
>      Project: Maven SCM
>         Type: Bug

>   Components: maven-scm-provider-perforce
>     Versions: 1.0
>     Reporter: John Didion
>     Assignee: Mike Perham
>     Priority: Critical
>      Fix For: 1.0
>  Attachments: PerforceChangeLogCommand.diff, svn.diff
>
>
> The PerforceChangeLogCommand as written does not work if the update was done with the client spec generated by the checkout/update command. The attached diff will fix the problem.

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