[ http://jira.codehaus.org/browse/SCM-165?page=comments#action_59481 ]
Mike Perham commented on SCM-165: --------------------------------- This patch fails when running the changelog command in standalone mode. Use the SCM plugin to run a changelog on some directory "mvn scm:changelog -DconnectionUrl=XXX" where XXX is your developerConnection string in the POM and you will find that the command fails due to the clientspec not existing. This is because your patch assumes it is always run after an update. Nonetheless, I'm inclined to think this is better than before since Continuum is the major user of the changelog command and it wasn't working for Continuum before. I'm assuming that most people don't use the SCM plugin except for testing. Emmanuel, do you have any opinion here? Would you rather see the changelog command only work as part of an update/checkout or not work with those but work standalone? > 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
