[jira] Commented: (SCM-165) PerforceChangeLogCommand needs to use the same clientspec as the update command
[ 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
[jira] Closed: (SCM-13) Investigate pure Java SVN interface
[ http://jira.codehaus.org/browse/SCM-13?page=all ] Emmanuel Venisse closed SCM-13: --- Assign To: Emmanuel Venisse Resolution: Fixed All patches are applied with some modifications like links to maven-settings that are removed. Thanks David This provider will be release when a new version of javasvn (1.0.4) will be release. This version will support file protocol so we'll can test it correctly with TCK. > Investigate pure Java SVN interface > --- > > Key: SCM-13 > URL: http://jira.codehaus.org/browse/SCM-13 > Project: Maven SCM > Type: Task > Components: maven-scm-provider-svn > Reporter: Brett Porter > Assignee: Emmanuel Venisse > Fix For: 1.0 > Attachments: SCM-13-maven-scm-api.patch, > SCM-13-maven-scm-manager-plexus.patch, SCM-13-maven-scm-plugin.patch, > SCM-13-maven-scm-provider-svn.tar.gz, ch.ethz.ganymed.tar.gz, > tmate.org.javasvn.tar.gz > > > There is this: http://tmate.org/svn/ > I'd say javahl is out because it requires native binaries. -- 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
[jira] Commented: (SCM-165) PerforceChangeLogCommand needs to use the same clientspec as the update command
[ http://jira.codehaus.org/browse/SCM-165?page=comments#action_59501 ] Emmanuel Venisse commented on SCM-165: -- update and changelog commands doesn't run necessarily as part of a single VM invocation. > 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
[jira] Commented: (SCM-165) PerforceChangeLogCommand needs to use the same clientspec as the update command
[ http://jira.codehaus.org/browse/SCM-165?page=comments#action_59500 ] Emmanuel Venisse commented on SCM-165: -- changelog command must work in standalone mode (require by changelog mojo and by changelog report mojo) AND as part of update command (require by update mojo and continuum). > 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
