[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

[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

[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 cli

[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