[
https://jira.codehaus.org/browse/MNG-4713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=328548#comment-328548
]
Brett Porter commented on MNG-4713:
-----------------------------------
I don't believe I misunderstood the comment. I understand that it could be
changed and work in many cases. However, I would not be sure that would not
break someone's build that is relying on that form of basedir.
I don't known what you mean by java.library.path - can you post an example
project that illustrates it?
I believe it is possible to create an extension that will populate the value in
a new variable (say, basedirFS), if that is what is needed.
> ${basedir} variable makes portable builds overly difficult
> ----------------------------------------------------------
>
> Key: MNG-4713
> URL: https://jira.codehaus.org/browse/MNG-4713
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Design, Patterns & Best Practices
> Affects Versions: 2.2.1
> Reporter: Gili
> Fix For: Issues to be reviewed for 3.x
>
>
> Please reopen MNG-3198. I believe that Brett misunderstood what Jochen wrote.
> There is no simple workaround with the current Maven implementation. Jochen
> was saying that Maven should use unix-style slashes under Windows for the
> sake of portability and let users convert to Windows-style slashes themselves
> if they wish to use an external script.
> Simple use-case: try passing a $\{basedir\}-relative path into the
> "java.library.path" property. It's impossible to do this portably under
> Maven's existing implementation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
