maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brett Porter (JIRA)" <>
Subject [jira] Commented: (MNG-3198) ${basedir} variable makes portable builds overly difficult
Date Thu, 24 Jun 2010 02:32:12 GMT


Brett Porter commented on MNG-3198:

please open an issue in the resources plugin if you need a feature to get the basedir using
unix-style separators. I don't believe this is needed in the core. I assume this is only for
test cases and plugins run through the build - note that you can also rely on the basedir
being the work directory, so you can use relative paths.

> ${basedir} variable makes portable builds overly difficult
> ----------------------------------------------------------
>                 Key: MNG-3198
>                 URL:
>             Project: Maven 2 & 3
>          Issue Type: Bug
>          Components: Design, Patterns & Best Practices, Logging, POM, POM::Encoding,
>    Affects Versions: 2.0.7
>            Reporter: Andrew J. Leer
>            Assignee: Brett Porter
>         Attachments: SimpleTest21.tar,
> Using log4j.xml I tried to use the resource filtering mechanism of Maven2 to write log
files to the directory:
> ${basedir}/logs
> (in windows)
> In the end the log files indeed do end up in the project directory, but not the ./log
> Also the name of the log file becomes the path with all of the '\' (${file.seprator}'s
taken out of it:
> For instance if the path to my log file was:
>      "C:\dev\workspace\project\logs\project-1.0-dev_test.log"
> My log file would appear in ${basedir} and be called:
>     "devworkspaceprojectlogsproject-1.0-dev_test.log"
> Thank you, 
>      Andrew J. Leer

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message