Support for slf4j-api about javamelody HOT 3 CLOSED

accepted because javamelody must not throw a classnotfoundexception.

Note that javamelody in a webapp is not supposed to depend on Log4J.
javamelody add a log4jappender to take warn logs of the application only if 
log4j is
present in the application.

The issue with classnotfoundexception comes from the fact that log4j-over-slf4j 
is
only a partial implementation of Log4J. So the availability of
org.apache.log4j.Logger is not sufficient to know if Log4J is available, which 
is
unintuitive to me.
Ref: http://www.slf4j.org/legacy.html#log4j-over-slf4j

The classnotfoundexception should be fixed with a test for the availability of
org.apache.log4j.AppenderSkeleton after testing the availability of
org.apache.log4.Logger. So you will be able to use log4j-over-slf4j. To monitor
logback warn logs, I have added the use of logback appender in the TODO list for
another day.

This fix is available in trunk and ready for next release (1.13)

Thanks, built a snapshot and tested it.

Code at
$ svn checkout
https://cia.svn.sourceforge.net/svnroot/cia/trunk/citizen-intelligence-agency
citizen-intelligence-agency

But already miss the log output in javamelody, will see if I have time to 
create a
patch someday.