I think your first idea was the best one. Just use a different profile at deploy time to change the log4j.properties filename.
If you want to stick with your second idea, a basic ant task should do the trick. On 6/30/06, Adam Hardy <[EMAIL PROTECTED]> wrote:
Hi, I would like to configure our m2 setup so that each developer can work with his/her own log4j.properties file, in testing and in deploy. One approach I looked at meant filtering the web.xml and appending the username to the log4j.properties setting, but this requires log4j.properties files for every user going into the final war, which I would like to avoid. Is there a plugin that will do copies, i.e. taking the username-log4j.properties, renaming it to 'log4j.properties' and moving it to the WEB-INF/classes dir? I can then exclude the 'username-lo4j.properties' files. Thanks, Adam --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
