[
http://jira.codehaus.org/browse/SCM-355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siarhei Dudzin updated SCM-355:
-------------------------------
Attachment: SCM-355-documentation.patch
I've also created a patch for documentation (in case it helps)
> CVS provider with SSPI transport does not support port number in url
> --------------------------------------------------------------------
>
> Key: SCM-355
> URL: http://jira.codehaus.org/browse/SCM-355
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-cvs
> Affects Versions: 1.0
> Environment: maven 2.0.7, CVSNT server configured non default port
> Reporter: Siarhei Dudzin
> Priority: Blocker
> Attachments: SCM-355-documentation.patch, SCM-355.patch
>
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
