maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Casey (JIRA)" <>
Subject [jira] Commented: (MNG-4210) Remove log4j configuration warning
Date Mon, 22 Jun 2009 15:36:15 GMT


John Casey commented on MNG-4210:

I'm planning to include - but shade, making it inaccessible to plugins and the outside world
- log4j 1.2.14. It seems that httpclient actually depends on clogging 1.0.4 (which is also
shaded in to avoid classloader conflicts with plugins), but that the logging strategy employed
by clogging actually looks for log4j classes by name on the classpath and will try to load
them if they exist. If a plugin depends on log4j and happens to be the trigger that causes
the http wagon, httpclient, and clogging to load, then clogging gets confused and tries to
use the log4j included with the plugin. This is causing quite a bit of trouble in these cases,
basically resulting in a stacktrace.

By including log4j in the core classpath, we can work around this strategy and make plugins
that depend on log4j safe to use. I'm still working on this issue, and if I can supply a configuration
for commons-logging that will allow us to leave out log4j, I'll do that instead.

> Remove log4j configuration warning
> ----------------------------------
>                 Key: MNG-4210
>                 URL:
>             Project: Maven 2
>          Issue Type: Improvement
>          Components: Logging
>    Affects Versions: 2.2.0
>            Reporter: Benjamin Bentmann
>            Assignee: John Casey
>            Priority: Trivial
>             Fix For: 2.2.0
> Running {{mvn help:active-profiles -U}} on a (minimal) POM delivers
> {noformat}
> [INFO] artifact org.apache.maven.plugins:maven-help-plugin: checking for updates from
> log4j:WARN No appenders could be found for logger (
> log4j:WARN Please initialize the log4j system properly.
> {noformat}
> We probably need to ship with a to silence this harmless noise.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message