[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

[jira] Commented: (SCM-168) PerforceChangeLogConsumer should use relative paths

[ http://jira.codehaus.org/browse/SCM-168?page=comments#action_59480 ] Mike Perham commented on SCM-168: - Are you diffing off of the maven 1.x SCM source code or an old beta or alpha, John? Your diff, while recognizable, does not match up with the latest

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

[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_59326 ] Mike Perham commented on SCM-165: - John, please attach a standard SVN diff. Your diff does not contain the filename headers. svn diff patch.diff PerforceChangeLogCommand needs to

[jira] Assigned: (SCM-165) PerforceChangeLogCommand needs to use the same clientspec as the update command

[ http://jira.codehaus.org/browse/SCM-165?page=all ] Mike Perham reassigned SCM-165: --- Assign To: Mike Perham PerforceChangeLogCommand needs to use the same clientspec as the update command

[jira] Resolved: (SCM-163) PerforceUpdateCommand does not correctly return change list

[ http://jira.codehaus.org/browse/SCM-163?page=all ] Mike Perham resolved SCM-163: - Resolution: Fixed PerforceUpdateCommand does not correctly return change list --- Key: SCM-163

[jira] Commented: (SCM-163) PerforceUpdateCommand does not correctly return change list

[ http://jira.codehaus.org/browse/SCM-163?page=comments#action_59327 ] Mike Perham commented on SCM-163: - Thanks for tracking this down, John. The code was written before the changelog command was well defined. PerforceUpdateCommand does not correctly

[jira] Resolved: (SCM-114) Clientspec naming

[ http://jira.codehaus.org/browse/SCM-114?page=all ] Mike Perham resolved SCM-114: - Resolution: Fixed Added path to clientspec name. Also added owner as a field since it was creating clientspecs without an owner before (I assumed it would associate

[jira] Assigned: (SCM-120) ClearCase Changelog test failure

[ http://jira.codehaus.org/browse/SCM-120?page=all ] mike perham reassigned SCM-120: --- Assign To: mike perham ClearCase Changelog test failure Key: SCM-120 URL: http://jira.codehaus.org/browse/SCM-120

[jira] Resolved: (SCM-120) ClearCase Changelog test failure

[ http://jira.codehaus.org/browse/SCM-120?page=all ] mike perham resolved SCM-120: - Resolution: Fixed Patch applied. ClearCase Changelog test failure Key: SCM-120 URL:

[jira] Commented: (SCM-120) ClearCase Changelog test failure

[ http://jira.codehaus.org/browse/SCM-120?page=comments#action_54811 ] mike perham commented on SCM-120: - I believe this issue is due to timezones. 10-Sep-03 GMT is 09-Sep-03 in my timezone (US Central time). Can you update the test to be a little more

[jira] Commented: (SCM-121) Intermittent CVS test failures

[ http://jira.codehaus.org/browse/SCM-121?page=comments#action_54813 ] mike perham commented on SCM-121: - I fixed the test failure reported by Dennis above. There are still failures in the Diff TCK test case. I can't figure out why they are breaking but I

[jira] Created: (SCM-122) Starteam test failures when running a full SCM build

Starteam test failures when running a full SCM build Key: SCM-122 URL: http://jira.codehaus.org/browse/SCM-122 Project: Maven SCM Type: Bug Components: maven-scm-provider-starteam Versions: 1.0-beta-3

[jira] Commented: (SCM-114) Clientspec naming

[ http://jira.codehaus.org/browse/SCM-114?page=comments#action_53488 ] mike perham commented on SCM-114: - The Perforce plugin will NOT obey P4CLIENT because it needs to support multiple clientspecs with Continuum. It will NOT obey P4PASSWD because it does

[jira] Commented: (SCM-113) Support persistent and transient clientspecs

[ http://jira.codehaus.org/browse/SCM-113?page=comments#action_53419 ] mike perham commented on SCM-113: - Good idea on the Description. Note that Maven SCM does not know anything about the context in which it is running. It does not know that it is

[jira] Commented: (SCM-110) Perforce should force sync

[ http://jira.codehaus.org/browse/SCM-110?page=comments#action_53295 ] mike perham commented on SCM-110: - If you do a release:perform, maven checks out the tagged source code to target/checkout and builds that to generate the official released binaries. If

[jira] Updated: (SCM-110) Perforce should force sync

[ http://jira.codehaus.org/browse/SCM-110?page=all ] mike perham updated SCM-110: Attachment: force2.txt Perforce should force sync -- Key: SCM-110 URL: http://jira.codehaus.org/browse/SCM-110 Project:

[jira] Created: (SCM-97) Implement executable changelog command

Implement executable changelog command -- Key: SCM-97 URL: http://jira.codehaus.org/browse/SCM-97 Project: Maven SCM Type: Bug Components: maven-scm-provider-perforce Versions: 1.0-beta-2 Reporter: mike perham

[jira] Created: (SCM-92) Add working directory support to Perforce update command

Add working directory support to Perforce update command Key: SCM-92 URL: http://jira.codehaus.org/browse/SCM-92 Project: Maven SCM Type: Bug Components: maven-scm-provider-perforce Versions:

[jira] Updated: (SCM-92) Add working directory support to Perforce update command

[ http://jira.codehaus.org/browse/SCM-92?page=all ] mike perham updated SCM-92: --- Attachment: update2.txt Revised patch to wrap checkout command in the update command itself rather than in the provider. Add working directory support to Perforce update

[jira] Created: (SCM-88) Add transparent support for locking providers

Add transparent support for locking providers - Key: SCM-88 URL: http://jira.codehaus.org/browse/SCM-88 Project: Maven SCM Type: Improvement Components: maven-scm-api Versions: 1.0-beta-2 Reporter: mike