[
https://issues.apache.org/jira/browse/SCM-581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17962138#comment-17962138
]
ASF GitHub Bot commented on SCM-581:
------------------------------------
jira-importer commented on issue #793:
URL: https://github.com/apache/maven-scm/issues/793#issuecomment-2964624410
**[Fredrik
Jonson](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=fredrikj)**
commented
The bug is in the DefaultUrlNormalizer class in the module
maven-model-builder, that is a part of maven-core, not maven-scm-plugin or the
scm hg provider.
The DefaultUrlNormalizer does the following to the element scm/connection:
result = result.replaceAll( "(?<![:/])/+", "/" );
Which removes any double slash after the hostname part of a url.
The normalization occurs when the release plugin doesn't find a ScmSourceUrl
in the plugin descriptor. Instead MavenProject.getScm().getConnection() is used
to retrieve a scm url. When that method returns the scm connection url is
"normalized" and that all so important double slash is removed.
See discussion here:
http://news.gmane.org/gmane.comp.jakarta.turbine.maven.devel/98099
> URL mangling should preserve double slashes
> -------------------------------------------
>
> Key: SCM-581
> URL: https://issues.apache.org/jira/browse/SCM-581
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-scm-provider-mercurial (hg)
> Affects Versions: 1.4
> Environment: Apache Maven 3.0 (r1004208; 2010-10-04 13:50:56+0200)
> Java version: 1.6.0_20
> Reporter: Andreas Sewe
> Assignee: Benjamin Bentmann
> Priority: Major
>
> AFAIK, Mercurial allows for URLs like
> {{ssh://example.org//home/sewe/example-project/}}. Unfortunately, the
> Mercurial SCM provider turns this into {{hg push
> ssh://example.org/home/sewe/example-project/}}, which fails if, e.g., the
> Mercurial server is configured to look for repositories in the user's home
> directory (may or may not be {{/home/sewe}}, depending on your login)
> *unless* an absolute path is explicitly requested by using a path starting
> with a double slash.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
