[SCM-168] PerforceChangeLogConsumer should use relative paths

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 1.0-beta-3
• Fix Version/s: 1.0-beta-3
• Component/s: maven-scm-provider-perforce
• Assignee: Mike Perham
• Reporter: John Didion
• Created: 23/Feb/06 13:29
• Updated: 27/Mar/06 16:10
• Resolved: 27/Mar/06 16:10

Description

It seems like all scm providers are dealing with relative paths, rather than absolute repository paths. PerforceCheckOutCommand is definitely doing this. PerforceChangeLogConsumer, however, does not, which means ChangeSet.containsFilename always returns false because it's comparing a relative path to an absolute one.

There are two changes. First, in PerforceChangeLogCommand:

PerforceChangeLogConsumer consumer = new PerforceChangeLogConsumer( ((PerforceScmProviderRepository) repo).getPath(), startDate, endDate );

The attached diff is for the second set of changes, which are to PerforceChangeLogConsumer.