[ http://jira.codehaus.org/browse/SCM-165?page=all ]
Mike Perham closed SCM-165.
---------------------------
Resolution: Fixed
John, I updated the changelog command as you mentioned. There is a
"maven.scm.persistcheckout" system property (see also
ScmProviderRepository.setPersistCheckout()) which will persist the clientspec
across invocations. Feel free to test this change and reopen if you find still
have problems.
> 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
> Issue Type: Bug
> Components: maven-scm-provider-perforce
> Affects Versions: 1.0-beta-3
> Reporter: John Didion
> Assigned To: 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
