[ http://jira.codehaus.org/browse/SCM-165?page=comments#action_59591 ]
Mike Perham commented on SCM-165: --------------------------------- Here's my understanding of the requirements: 1) Continuum needs to be able to run update/checkout and changelog in the same VM when running a build. Since this uses a persistent clientspec, the changelog command needs to reuse the same clientspec. That's what this bug is about and it should work with my changes 3 days ago. 2) The changelog mojo needs to be able to run the changelog command as a standalone feature. The command should default to NO clientspec but allow the user to pass in a clientspec on the command line. 3) The user should be able to run 'mvn scm:update scm:changelog' to get results similar to (1) and 'mvn scm:changelog' to get results similar to (2). Any comments? Any other usecases? > 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
