[
https://jira.codehaus.org/browse/MNG-4713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=348030#comment-348030
]
Jason van Zyl commented on MNG-4713:
------------------------------------
Make a self contained project which is a demonstration of the problem that I
can run. Otherwise I consider it incomplete and I'm doing this with all the
issues. I don't have time to reconstruct test projects for all problems that
are reported before I can reproduce them and test them.
> ${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 was sent by Atlassian JIRA
(v6.1.6#6162)
