Hi, while running the camel's own test cases one can't see the logs directly in his IDE as always the 'org.apache.log4j.FileAppender' is used/active in log4j.properties under camel-xyz/src/test/resources/log4j.properties. So you always have to switch from your IDE to the redirected outputs in target/camel-xyz-test.log to see the logs. To me this was annoying but don't know what others think about it. Other than that while changing/working on the camel code & running the unit-tests the Camel Riders would prefer to see the logs directly in their IDE, I assume!
On the other hand, I think the reason for that was not to flood the maven console while doing 'mvn test', 'mvn install', etc. right? IMHO I think one can change them to out instead of file, that's log4j.rootLogger='LOG_LEVEL', out But instruct sunfire-plugin in [1] (a pluginManagment entry in there) to redirect the output to files through the option [2]. Would it make sense to you? At least that's the way I do it by my client's projects. [1] https://svn.apache.org/repos/asf/camel/trunk/parent/pom.xml [2] http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html#redirectTestOutputToFile Regards, Babak -- View this message in context: http://camel.465427.n5.nabble.com/log4j-properties-in-camel-tp4723887p4723887.html Sent from the Camel - Users mailing list archive at Nabble.com.
