Hi folks! My name is Mark and I had a few discussions about log4j 2.0 with Ralph lately. It is about the question whether log4j-2.0 would be a candidate for all the internal logging of Apache Maven or not.
I've checked out the sources they build fine. I'm not a logging expert, but more a casual programmer, so please excuse any dumb questions: 1.) is the logging implementation pluggable? 2.) is there an optional support for ThreadContextClassLoader scenarios? This is often a problem for logging in libraries which are on a shared classpath. Imagine 2 webapps, both using OpenWebBeans as CDI container. One webapp sets the org.apache.webbeans loglevel to debug, the other wone to WARN ... 3.) I've seen that the API now uses ellipsis parameters. Wouldn't it be better to re-position the Throwable parameter before the String parameter? Otherwise that might interfere with the Object... parameter, isn't? 4.) How much work is left to do before you could perform a first 'teaser release'? For starting with using log4j we would at least need anything which got released. txs and LieGrue, strub --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
