[ http://jira.codehaus.org/browse/SCM-165?page=comments#action_59517 ]
Mike Perham commented on SCM-165: --------------------------------- I don't see how I can make this work in all cases without forcing the user to provide a parameter or use something like the release.properties file that the release plugin uses. I will brainstorm tonight and come up with the best compromise I can. > 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 > 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
