maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brett Porter (JIRA)" <>
Subject [jira] (MNG-4713) ${basedir} variable makes portable builds overly difficult
Date Sat, 13 Jul 2013 05:14:05 GMT


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

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:
>             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:

View raw message