maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Osipov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MNG-6386) ${project.baseUri} is not a valid URI (according to RFC 3986)
Date Wed, 02 May 2018 22:23:00 GMT

     [ https://issues.apache.org/jira/browse/MNG-6386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Michael Osipov updated MNG-6386:
--------------------------------
    Description: 
{{File#toURI}} produces an invalid URI on Windows:
{noformat}
file:/C:/path/to/basedir{noformat}
A valid URI has to be:
{noformat}
file:///C:/path/to/basedir{noformat}

Same issue for Unix-like OSes:
{noformat}
file:/path/to/basedir{noformat}
A valid URI has to be:
{noformat}
file:///path/to/basedir{noformat}

Using {{Path#toUri}} we can easily solve that problem because it creates compliant URIs. The
failure occurs when interacting with local Git and Subversion repos:

{noformat}
PS D:\Entwicklung\Projekte\maven-scm> svn ls file:/D:/Entwicklung/svn-repos/scm-svn-test-at-sign
svn: E020024: Error resolving case of 'file:\D:\Entwicklung\svn-repos\scm-svn-test-at-sign'

while the proper (new) havior will produce a valid URI:
PS D:\Entwicklung\Projekte\maven-scm> svn ls file:///D:/Entwicklung/svn-repos/scm-svn-test-at-sign
branches/
tags/
trunk/ 
{noformat}

{noformat}
PS D:\Entwicklung\Projekte> git clone file:///D:/Entwicklung/git-repos/toll tlll2
Cloning into 'tlll2'...
warning: You appear to have cloned an empty repository.
PS D:\Entwicklung\Projekte> git clone file:/D:/Entwicklung/git-repos/toll tlll2
Cloning into 'tlll2'...
ssh: Could not resolve hostname file: Name or service not known
fatal: Could not read from remote repository.
{noformat}

or Subversion repo at: {{D:\Entwicklung\svn-repos\это по-русский}}:
{noformat}
PS D:\Entwicklung\Projekte> svn ls file:/D:/Entwicklung/svn-repos/это%20по-русский/
svn: E020024: Error resolving case of 'file:\D:\Entwicklung\svn-repos\???%20??-???????\'
{noformat}

proper URI gives:
{noformat}
PS D:\Entwicklung\Projekte> svn ls file:///D:/Entwicklung/svn-repos/%D1%8D%D1%82%D0%BE%20%D0%BF%D0%BE-%D1%80%D1%83%D1%81%D1%81%D0%BA%D0%B8%D0%B9/
branches/
tags/
trunk/
{noformat}

  was:
{{File#toURI}} produces an invalid URI on Windows:
{noformat}
file:/C:/path/to/basedir{noformat}
A valid URI has to be:
{noformat}
file:///C:/path/to/basedir{noformat}

Same issue for Unix-like OSes:
{noformat}
file:/path/to/basedir{noformat}
A valid URI has to be:
{noformat}
file:///path/to/basedir{noformat}

Using {{Path#toUri}} we can easily solve that problem because it creates compliant URIs. The
failure occurs when interacting with local Git and Subversion repos:

{noformat}
PS D:\Entwicklung\Projekte\maven-scm> svn ls file:/D:/Entwicklung/svn-repos/scm-svn-test-at-sign
svn: E020024: Error resolving case of 'file:\D:\Entwicklung\svn-repos\scm-svn-test-at-sign'

while the proper (new) havior will produce a valid URI:
PS D:\Entwicklung\Projekte\maven-scm> svn ls file:///D:/Entwicklung/svn-repos/scm-svn-test-at-sign
branches/
tags/
trunk/ 
{noformat}

{noformat}
PS D:\Entwicklung\Projekte> git clone file:///D:/Entwicklung/git-repos/toll tlll2
Cloning into 'tlll2'...
warning: You appear to have cloned an empty repository.
PS D:\Entwicklung\Projekte> git clone file:/D:/Entwicklung/git-repos/toll tlll2
Cloning into 'tlll2'...
ssh: Could not resolve hostname file: Name or service not known
fatal: Could not read from remote repository.
{noformat}


> ${project.baseUri} is not a valid URI (according to RFC 3986)
> -------------------------------------------------------------
>
>                 Key: MNG-6386
>                 URL: https://issues.apache.org/jira/browse/MNG-6386
>             Project: Maven
>          Issue Type: Bug
>    Affects Versions: 3.5.3
>            Reporter: Michael Osipov
>            Assignee: Michael Osipov
>            Priority: Major
>             Fix For: 3.5.4-candidate
>
>
> {{File#toURI}} produces an invalid URI on Windows:
> {noformat}
> file:/C:/path/to/basedir{noformat}
> A valid URI has to be:
> {noformat}
> file:///C:/path/to/basedir{noformat}
> Same issue for Unix-like OSes:
> {noformat}
> file:/path/to/basedir{noformat}
> A valid URI has to be:
> {noformat}
> file:///path/to/basedir{noformat}
> Using {{Path#toUri}} we can easily solve that problem because it creates compliant URIs.
The failure occurs when interacting with local Git and Subversion repos:
> {noformat}
> PS D:\Entwicklung\Projekte\maven-scm> svn ls file:/D:/Entwicklung/svn-repos/scm-svn-test-at-sign
> svn: E020024: Error resolving case of 'file:\D:\Entwicklung\svn-repos\scm-svn-test-at-sign'
> while the proper (new) havior will produce a valid URI:
> PS D:\Entwicklung\Projekte\maven-scm> svn ls file:///D:/Entwicklung/svn-repos/scm-svn-test-at-sign
> branches/
> tags/
> trunk/ 
> {noformat}
> {noformat}
> PS D:\Entwicklung\Projekte> git clone file:///D:/Entwicklung/git-repos/toll tlll2
> Cloning into 'tlll2'...
> warning: You appear to have cloned an empty repository.
> PS D:\Entwicklung\Projekte> git clone file:/D:/Entwicklung/git-repos/toll tlll2
> Cloning into 'tlll2'...
> ssh: Could not resolve hostname file: Name or service not known
> fatal: Could not read from remote repository.
> {noformat}
> or Subversion repo at: {{D:\Entwicklung\svn-repos\это по-русский}}:
> {noformat}
> PS D:\Entwicklung\Projekte> svn ls file:/D:/Entwicklung/svn-repos/это%20по-русский/
> svn: E020024: Error resolving case of 'file:\D:\Entwicklung\svn-repos\???%20??-???????\'
> {noformat}
> proper URI gives:
> {noformat}
> PS D:\Entwicklung\Projekte> svn ls file:///D:/Entwicklung/svn-repos/%D1%8D%D1%82%D0%BE%20%D0%BF%D0%BE-%D1%80%D1%83%D1%81%D1%81%D0%BA%D0%B8%D0%B9/
> branches/
> tags/
> trunk/
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message