I have my junit tests setup to fork (maven.junit.fork=true) which causes all log4j INFO and above messages to go to STDOUT when my build process starts running the unit tests.
I have my build process copy log4j.properties over to target/classes (so it's in the classpath). What's the next step I should take to get my unit tests to pick up my log4j.properties? Just putting it in the classpath does not seem to be enough. Ideally I'd like to set something in project.properties so that every time I run my build it uses my log4j.properties. Thanks for the help! -Todd --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
