[
https://issues.apache.org/jira/browse/SCM-877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17965040#comment-17965040
]
Olivier Lamy commented on SCM-877:
----------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-scm#1107|https://github.com/apache/maven-scm/issues/1107]. Please
visit the GitHub issue to view further activity, add comments, or subscribe to
receive notifications.
> AbstractSvnScmProvider#parseScmUrl() accepts file URLs with backslashes while
> SvnTagBranchUtils cannot handle them
> ------------------------------------------------------------------------------------------------------------------
>
> Key: SCM-877
> URL: https://issues.apache.org/jira/browse/SCM-877
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-scm-provider-svn
> Affects Versions: 1.9.5
> Reporter: Michael Osipov
> Priority: Major
>
> Subversion accepts URLs in the form:
> {noformat}
> svn co file:///D:\my\repo{noformat}
> While this URL is invalid, it is still parsed properly. Using the same URL in
> {{<developerConnection />}} makes SvnTagBranchUtils completely fail in path
> calculation because it does not handle backslashes at all.
>
> The proposed solution is that {{parseUrl()}} will test file URLs for
> backslashes and reject them since they are invalid anyway.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
