You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org> on 2009/06/18 20:34:15 UTC
[jira] Created: (MNG-4210) Remove log4j configuration warning
Remove log4j configuration warning
----------------------------------
Key: MNG-4210
URL: http://jira.codehaus.org/browse/MNG-4210
Project: Maven 2
Issue Type: Improvement
Components: Logging
Affects Versions: 2.2.0
Reporter: Benjamin Bentmann
Priority: Trivial
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 central
log4j:WARN No appenders could be found for logger (hidden.org.apache.commons.httpclient.params.DefaultHttpParams).
log4j:WARN Please initialize the log4j system properly.
{noformat}
We probably need to ship with a log4j.properties to silence this harmless noise.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-4210) Remove log4j configuration warning
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Casey updated MNG-4210:
----------------------------
Assignee: John Casey
Fix Version/s: 2.2.0
I'm adding a log4j.properties file to $maven.home/conf so users can configure this to tune the output for the httpclient-based http wagon (possibly among other things). Likewise, embedders won't have to deal with collisions on this file, since they're likely to use the jars directly instead of the distro...and users with a different config file can always remove this file from their distro if it's in the way.
I've already made these changes on my localhost, just need to run the ITs to verify them.
> Remove log4j configuration warning
> ----------------------------------
>
> Key: MNG-4210
> URL: http://jira.codehaus.org/browse/MNG-4210
> 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 central
> log4j:WARN No appenders could be found for logger (hidden.org.apache.commons.httpclient.params.DefaultHttpParams).
> log4j:WARN Please initialize the log4j system properly.
> {noformat}
> We probably need to ship with a log4j.properties to silence this harmless noise.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-4210) Remove log4j configuration warning
Posted by "Mark Hobson (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=181066#action_181066 ]
Mark Hobson commented on MNG-4210:
----------------------------------
Can you clarify why log4j is being shipped with Maven? Does HttpClient have a hard dependency on log4j and not go via commons-logging?
> Remove log4j configuration warning
> ----------------------------------
>
> Key: MNG-4210
> URL: http://jira.codehaus.org/browse/MNG-4210
> 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 central
> log4j:WARN No appenders could be found for logger (hidden.org.apache.commons.httpclient.params.DefaultHttpParams).
> log4j:WARN Please initialize the log4j system properly.
> {noformat}
> We probably need to ship with a log4j.properties to silence this harmless noise.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-4210) Remove log4j configuration warning
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Casey closed MNG-4210.
---------------------------
Resolution: Fixed
I've moved Maven to use jcl-over-slf4j and slf4j-jdk14 in place of commons-logging and log4j. This solves the classloading exceptions from MNG-4207 and cleans up the log4j configuration warnings from this issue simultaneously.
> Remove log4j configuration warning
> ----------------------------------
>
> Key: MNG-4210
> URL: http://jira.codehaus.org/browse/MNG-4210
> 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 central
> log4j:WARN No appenders could be found for logger (hidden.org.apache.commons.httpclient.params.DefaultHttpParams).
> log4j:WARN Please initialize the log4j system properly.
> {noformat}
> We probably need to ship with a log4j.properties to silence this harmless noise.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Reopened: (MNG-4210) Remove log4j configuration warning
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Casey reopened MNG-4210:
-----------------------------
still not quite fixed. Need to revisit.
> Remove log4j configuration warning
> ----------------------------------
>
> Key: MNG-4210
> URL: http://jira.codehaus.org/browse/MNG-4210
> 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 central
> log4j:WARN No appenders could be found for logger (hidden.org.apache.commons.httpclient.params.DefaultHttpParams).
> log4j:WARN Please initialize the log4j system properly.
> {noformat}
> We probably need to ship with a log4j.properties to silence this harmless noise.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-4210) Remove log4j configuration warning
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=181125#action_181125 ]
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: http://jira.codehaus.org/browse/MNG-4210
> 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 central
> log4j:WARN No appenders could be found for logger (hidden.org.apache.commons.httpclient.params.DefaultHttpParams).
> log4j:WARN Please initialize the log4j system properly.
> {noformat}
> We probably need to ship with a log4j.properties to silence this harmless noise.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-4210) Remove log4j configuration warning
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Casey closed MNG-4210.
---------------------------
Resolution: Fixed
> Remove log4j configuration warning
> ----------------------------------
>
> Key: MNG-4210
> URL: http://jira.codehaus.org/browse/MNG-4210
> 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 central
> log4j:WARN No appenders could be found for logger (hidden.org.apache.commons.httpclient.params.DefaultHttpParams).
> log4j:WARN Please initialize the log4j system properly.
> {noformat}
> We probably need to ship with a log4j.properties to silence this harmless noise.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-4210) Remove log4j configuration warning
Posted by "Mark Hobson (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=181187#action_181187 ]
Mark Hobson commented on MNG-4210:
----------------------------------
Sounds good to me, thanks for the summary.
> Remove log4j configuration warning
> ----------------------------------
>
> Key: MNG-4210
> URL: http://jira.codehaus.org/browse/MNG-4210
> 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 central
> log4j:WARN No appenders could be found for logger (hidden.org.apache.commons.httpclient.params.DefaultHttpParams).
> log4j:WARN Please initialize the log4j system properly.
> {noformat}
> We probably need to ship with a log4j.properties to silence this harmless noise.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-4210) Remove log4j configuration warning
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=181155#action_181155 ]
John Casey commented on MNG-4210:
---------------------------------
BTW, slf4j is shaded into the maven distribution now, so plugins using slf4j will get their own versions loaded into their classloaders.
> Remove log4j configuration warning
> ----------------------------------
>
> Key: MNG-4210
> URL: http://jira.codehaus.org/browse/MNG-4210
> 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 central
> log4j:WARN No appenders could be found for logger (hidden.org.apache.commons.httpclient.params.DefaultHttpParams).
> log4j:WARN Please initialize the log4j system properly.
> {noformat}
> We probably need to ship with a log4j.properties to silence this harmless noise.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira