[SCM-355] CVS provider with SSPI transport does not support port number in url

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 1.0
• Fix Version/s: 1.1
• Component/s: maven-scm-provider-cvs
• Environment: maven 2.0.7, CVSNT server configured non default port
• Flags: Patch
• Assignee: Emmanuel Venisse
• Reporter: Siarhei Dudzin
• Created: 28/Nov/07 04:17
• Updated: 05/Apr/15 14:53
• Resolved: 09/May/08 04:25

Description

Current implementation has checks on harcoded number of delimiters which is for which doesn't allow to use port number in the url (which is happening when the server is configured to use a different port number). Having port number in the url tells SCM CVS that there are in fact 5 tokens which results in an exception with the following message:

>mvn scm:checkout

[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'scm'.
[INFO] ----------------------------------------------------------------------------
[INFO] Building saar-main
[INFO] task-segment: [scm:checkout] (aggregator-style)
[INFO] ----------------------------------------------------------------------------
[INFO] [scm:checkout]
[ERROR] The connection string contains an incorrect number of tokens (should be four).
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Cannot run checkout command :

Embedded error: Can't load the scm provider.
The scm url is invalid.

The following format of developerConnection is used: scm:cvs:sspi:<host>:<port>:<module>:<path>

If I remove the port number from the url it actually tries to checkout but fails as there is no response on that port. If I try to use the same cvs command maven is trying to issue (adding with the correct port number) - the checkout works.