Another option would be to move the "restricted" log4j.properties file into
something like src/test/log4j and then add a system property to surefire
configuration to pick it up from there. When running with maven, it would be
used. When running in your IDE, it wouldn't be picked up and the
Hi Willem,
thanks for your feedback.
Imagine your are working on a patch and there you do some LOGGER.trace() ,
debug(), info() etc.
Wouldn't you prefer to see your *new* log statements directly in your IDE
while unit-testing *your* changes to verify if the patch's log entries seem
as you expect
Hi
I'm only care about the log when there are some thing is wrong or the
test is failed. So I'm OK to store the log in the file.
If you are working on the application code which use camel as a lib, you
can always override the log4j.properties in your application.
Willem
On 8/23/11 2:17 PM, b
Hi Ben,
thanks for your reply.
To make it concrete, the pluginManagment entry in [1] would be something
like:
...
...
org.apache.maven.plugins
maven-surefire-plugin
true
true
...
...
And for example in the case of camel-core, the change in [2] would be *out
I haven't tried your approach myself, but I agree that being able to see the
output in the IDE console is ideal. I just modify the log4j.properties file
locally (and ignore it from SVN) to do this...but would be nice to avoid
doing this if possible...
bvahdat wrote:
>
> Hi,
>
> while running t
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
targ
