[
https://issues.apache.org/jira/browse/SCM-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17961150#comment-17961150
]
ASF GitHub Bot commented on SCM-355:
------------------------------------
jira-importer opened a new issue, #576:
URL: https://github.com/apache/maven-scm/issues/576
**[Siarhei
Dudzin](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=svadu)**
opened
**[SCM-355](https://issues.apache.org/jira/browse/SCM-355?redirect=false)** and
commented
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.
---
**Affects:** 1.0
**Attachments:**
-
[SCM-355.patch](https://issues.apache.org/jira/secure/attachment/12718545/SCM-355.patch)
(_2.67 kB_)
-
[SCM-355-documentation.patch](https://issues.apache.org/jira/secure/attachment/12718887/SCM-355-documentation.patch)
(_2.25 kB_)
> CVS provider with SSPI transport does not support port number in url
> --------------------------------------------------------------------
>
> Key: SCM-355
> URL: https://issues.apache.org/jira/browse/SCM-355
> Project: Maven SCM (Moved to GitHub Issues)
> 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
> Assignee: Emmanuel Venisse
> Priority: Blocker
> Fix For: 1.1
>
> 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 was sent by Atlassian Jira
(v8.20.10#820010)
