[Owasp-appsensor-dev] Issue 7 in appsensor: custom log4j.xml in 0.1.3.2

appsensor at googlecode.com appsensor at googlecode.com
Sun Jun 19 11:54:23 EDT 2011


Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 7 by matthias... at gmail.com: custom log4j.xml in 0.1.3.2
http://code.google.com/p/appsensor/issues/detail?id=7

Hi AppSensor-Team,

I've noticed strange logging behaviour after I added AppSensor 0.1.3.2 to  
my maven project. Found out that a custom log4j.xml file is bundled with  
the AppSensor-0.1.3.2.jar. Therefore the logging of the host application  
gets messed up when log4j is used. "messed up" means that the host log4j  
config is not respected and logging goes to /tmp/AppSensor.

I patched the 0.1.3.2 jar for my needs (removed logj4.*) and logging works  
like a charm again.

Is there any reason to ship a custom log4j.xml in the jar?

Bye4now,
Matthias Sefrin



More information about the Owasp-appsensor-dev mailing list