[MNG-3198] ${basedir} variable makes portable builds overly difficult

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 2.0.7
• Component/s: Design, Patterns & Best Practices, Logging, POM, POM::Encoding, Profiles
• Assignee: Brett Porter
• Reporter: Andrew J. Leer
• Created: 07/Sep/07 10:07
• Updated: 23/Jun/10 21:32
• Resolved: 29/Oct/07 19:31

Description

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

Issue Links

• relates to: MNG-4713 ${basedir} variable makes portable builds overly difficult

Sub-Tasks

• Create a variable called ${basedir.log4j}: Closed