[SCM-647] SvnChangeLogConsumer parses filename incorrectly when file is copied from existing one

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.5, 1.6
• Fix Version/s: 1.6
• Component/s: maven-scm-provider-svn
• Flags: Patch
• Assignee: Olivier Lamy
• Reporter: Petr Kozelka
• Created: 25/Nov/11 19:38
• Updated: 05/Apr/15 14:54
• Resolved: 28/Nov/11 08:56

Description

Current implementations uses non-xml svn log for gathering information. It always returns everything after 5th char as the filename, which is a bug in cases like this:

A /maven/scm/trunk/maven-scm-test/src/main/java/org/apache/maven/scm/ScmTestCase.java (from /maven/scm/trunk/maven-scm-api/src/main/java/org/apache/maven/scm/ScmTestCase.java:191665)

which indicate copying a path from existing revision.

Note that this example was taken from the svnlog2.txt line 510 file in test resources.

I suggest to fix it with the attached patch. It also enhances tests to assert that the parsed filenames are correct - not containing spaces and beginning with common path.