[SCM-986] SvnExe's SvnRemoteInfoCommand incorrectly implemented

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.12.2, 2.0.0-M1
• Fix Version/s: 2.0.0-M2
• Component/s: maven-scm-provider-svn
• Assignee: Michael Osipov
• Reporter: Michael Osipov
• Created: 22/May/22 20:16
• Updated: 25/May/22 10:40
• Resolved: 25/May/22 08:51

Description

Several bugs:

1st bug:
This class claims to process the following URLs:

• http://svn.apache.org/repos/asf/maven/maven-3/trunk
• http://svn.apache.org/repos/asf/maven/maven-3/trunk/

to http://svn.apache.org/repos/asf/maven/maven-3. The first URL works, but the second is processed to /svn.apache.org/repos/asf/maven/maven-3/trunk.

2nd bug:
Extracting branches happens with cl.createArg().setValue( baseUrl + "/tags" + "@" ); instead of cl.createArg().setValue( baseUrl + "/branches" + "@" );

3rd bug:
new LsConsumer() receives the new, reduced base URL as constructor arg and contructs the final tag/branch URLs as: http://svn.apache.org/repos/asf/maven/maven-3/maven-3.0 and http://svn.apache.org/repos/asf/maven/maven-3/maven-3.x. The path segments tags and branches are never passed.

Branch SCM-986 includes an extended TCK test to verify this faulty behavior.

Issue Links

• links to: GitHub Pull Request #145