You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@apache.org> on 2018/05/26 22:26:00 UTC
[jira] [Assigned] (SCM-877) AbstractSvnScmProvider#parseScmUrl()
accepts file URLs with backslashes while SvnTagBranchUtils cannot handle
them
[ https://issues.apache.org/jira/browse/SCM-877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Osipov reassigned SCM-877:
----------------------------------
Assignee: (was: Michael Osipov)
> 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
> 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
(v7.6.3#76005)