[ http://jira.codehaus.org/browse/SCM-165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_88557 ]
Anton Katernoga commented on SCM-165: ------------------------------------- I've found a problem related to system property approach which appears in continuum, I've filed it as C's issue CONTINUUM-1183. But it's an scm bug and I think it should be fixed in the scope of this issue. > 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-beta-4 > > 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
