[
https://jira.codehaus.org/browse/SCM-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=300550#comment-300550
]
Benoit Guerin commented on SCM-508:
---
any update on this ?
It is (for me) a blocker bug :
we are using DVCS, so we except not to clone from Internet when releasing. And
from now, with this bug, the only way to release from Windows PC is to let
localCheckout to false in the maven-release-plugin configuration ...
Wrong scm url validation for mercurial provider
---
Key: SCM-508
URL: https://jira.codehaus.org/browse/SCM-508
Project: Maven SCM
Issue Type: Bug
Components: maven-scm-provider-mercurial (hg)
Reporter: Alexander Nemish
Fix For: 1.x
Attachments: SCM-508-maven-scm-provider-hg.patch
According to documentation (http://maven.apache.org/scm/mercurial.html) scm
url can be of this form:
scm:hg:file://C:/dev/project/v3
but it doesn't work due to a bug in
https://svn.apache.org/repos/asf/maven/scm/tags/maven-scm-1.2/maven-scm-providers/maven-scm-provider-hg/src/main/java/org/apache/maven/scm/provider/hg/HgScmProvider.java
private HgUrlParserResult parseScmUrl( String scmSpecificUrl )
line 104: if ( !url.startsWith( file:/// ) !url.startsWith(
file://localhost/ ) )
The fix might be the following (like in svn provider)
line 104: if ( !url.startsWith( file:// ) !url.startsWith(
file://localhost/ ) )
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
