Hi Ben,
thanks for your reply.
To make it concrete, the pluginManagment entry in [1] would be something
like:
<build>
<pluginManagement>
...
...
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<configuration>
<redirectTestOutputToFile>true</redirectTestOutputToFile>
<failIfNoTests>true</failIfNoTests>
</configuration>
</plugin>
...
...
</pluginManagement>
</build>
And for example in the case of camel-core, the change in [2] would be *out*
instead of *file*.
log4j.rootLogger=INFO, out
I wonder what others think about this...
[1] https://svn.apache.org/repos/asf/camel/trunk/parent/pom.xml
[2]
https://svn.apache.org/repos/asf/camel/trunk/camel-core/src/test/resources/log4j.properties
Regards, Babak
--
View this message in context:
http://camel.465427.n5.nabble.com/log4j-properties-in-camel-tp4723887p4725617.html
Sent from the Camel - Users mailing list archive at Nabble.com.
