[
https://issues.apache.org/jira/browse/MNG-3760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16420891#comment-16420891
]
Michael Osipov commented on MNG-3760:
-------------------------------------
The given solution does to provide an RFC-compliant URL on Windows.
> Support property ${baseurl} to get RFC-compliant URL of project base directory
> ------------------------------------------------------------------------------
>
> Key: MNG-3760
> URL: https://issues.apache.org/jira/browse/MNG-3760
> Project: Maven
> Issue Type: New Feature
> Components: Artifacts and Repositories, Inheritance and Interpolation
> Affects Versions: 2.0.9
> Reporter: Benjamin Bentmann
> Assignee: Brett Porter
> Priority: Minor
> Fix For: 2.1.0, 3.0-alpha-3
>
>
> If people currently need a URL to their project base directory or any file
> within, they need to write {{file://$\{basedir}}/}}. The problem about this
> approach is that it doesn't deliver a [RFC-compliant
> URL|http://tools.ietf.org/html/rfc3986] since characters are not properly
> percent-encoded. Also, the exact number of slashes between {{file:}} and
> {{${basedir}}} depends on the OS (e.g. {{file:///C:/user/}} and
> {{file:///home/user}}, Unix paths have a leading slash by themselves, Windows
> not). This makes it currently impossible to configure plugins that expect a
> URL as input and do strict URL parsing.
> For this reason, I suggest to support an additional property {{${baseurl}}}
> with the value
> {code:java}
> baseurl = new File( basedir ).toURI().toString()
> {code}
> for POM interpolation.
> Some day, when Maven/Wagon itself handle percent-encoded {{file:}} URLs
> correctly (WAGON-111), this property could also be used to define local
> deployment repos like we commonly use for testing.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
