[ 
https://issues.apache.org/jira/browse/SCM-877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17963489#comment-17963489
 ] 

ASF GitHub Bot commented on SCM-877:
------------------------------------

jira-importer opened a new issue, #1107:
URL: https://github.com/apache/maven-scm/issues/1107

   **[Michael 
Osipov](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=michael-o)**
 opened 
**[SCM-877](https://issues.apache.org/jira/browse/SCM-877?redirect=false)** and 
commented
   
   Subversion accepts URLs in the form:
   
   ```
   svn co file:///D:\my\repo
   ```
   
   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.
   
   
   ---
   
   **Affects:** 1.9.5
   
   **Issue Links:**
   - [MNG-6386](https://issues.apache.org/jira/browse/MNG-6386) 
${project.baseUri} is not a valid URI (according to RFC 3986)
    (_**"depends upon"**_)
   




> 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)

Reply via email to