[
http://jira.codehaus.org/browse/MNG-3198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=201866#action_201866
]
Mark Michaelis commented on MNG-3198:
-------------------------------------
Actually this is a real problem. Especially when working together with the
config-processor-plugin.
I have a property which is defined as:
{code}
${basedir}/somepath
{code}
Now the config-processor-plugin will write a property file containing:
{code}
somepath=C:\dev/somepath
{code}
And Java will fail to read this property file as it reads:
{code}
C:dev/somepath
{code}
So this would be no problem if basedir uses slashes as file separators.
> ${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
> Assignee: Brett Porter
> 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
