maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gili (JIRA)" <j...@codehaus.org>
Subject [jira] (MNG-4713) ${basedir} variable makes portable builds overly difficult
Date Mon, 08 Jul 2013 03:07:05 GMT

     [ https://jira.codehaus.org/browse/MNG-4713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Gili updated MNG-4713:
----------------------

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

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

    
> ${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

Mime
View raw message