You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Paul Benedict (JIRA)" <ji...@codehaus.org> on 2010/01/31 01:04:55 UTC
[jira] Commented: (MNG-4464) Improve handling of relative paths
with backslashes
[ http://jira.codehaus.org/browse/MNG-4464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208688#action_208688 ]
Paul Benedict commented on MNG-4464:
------------------------------------
I opt for a warning to be produced in 3.0 and trigger an error in 3.1. To "encourage the user", warnings are the best means.
> Improve handling of relative paths with backslashes
> ---------------------------------------------------
>
> Key: MNG-4464
> URL: http://jira.codehaus.org/browse/MNG-4464
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: POM
> Affects Versions: 2.2.1, 3.0-alpha-4
> Environment: Unix, Mac
> Reporter: Benjamin Bentmann
> Priority: Minor
>
> Consider this snippet:
> {code:xml}
> <parent>
> <relativePath>..\pom.xml</relativePath>
> </parent>
> {code}
> Note in particular the backslash used in the path. While this path will be properly resolved on a Windows box, it will fail to resolve the local parent on a Unix/Mac box (as the backslash is not a separator but escape character here). This applies to other paths in the POM as well.
> For platform-independent behavior, we should either encourage the user to use forward slashes (by means of validation warnings/errors) or have Maven convert the paths internally.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira