[
http://jira.codehaus.org/browse/MNG-3198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106950
]
Jochen Wiedmann commented on MNG-3198:
--------------------------------------
Note, that you can safely use C:/dev/workspace/... even on Windows. In other
words, the requirement to distinguish between / and \\ will most likely only
be present when running an external batch script or something like that.
However, if you do that, then you are platform dependent anyways and should use
platform specific profiles, in which case file.separator would simply make the
POM unreadable.
> ${basedir} variable makes portable builds overly difficult
> ----------------------------------------------------------
>
> Key: MNG-3198
> URL: http://jira.codehaus.org/browse/MNG-3198
> Project: Maven 2
> Issue Type: Bug
> Components: Design, Patterns & Best Practices, Logging, POM,
> POM::Encoding, Profiles
> Affects Versions: 2.0.7
> Reporter: Andrew J. Leer
> Attachments: SimpleTest21.tar, SimpleTest21.zip
>
>
> 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 directory.
> 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:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
