Details
-
Bug
-
Status: Resolved (View Workflow)
-
Major
-
Resolution: Fixed
-
None
-
Platform: All, OS: All
Description
Hello,
I have noticed these warning after I performed an Hudson upgrade from 1.317 to
1.318
SLF4J: This version of SLF4J requires log4j version 1.2.12 or later. See also
http://www.slf4j.org/codes.html#log4j_version
log4j:WARN No appenders could be found for logger
(org.apache.commons.beanutils.converters.BooleanConverter).
log4j:WARN Please initialize the log4j system properly.
Constructor called: 15 false
Constructor called: 30 true
Constructor called: 10 false
Constructor called: 10 false
Constructor called: 15 false
Constructor called: 15 false
Constructor called: 10 false
Constructor called: 15 false
Constructor called: 15 false
Constructor called: 15 false
Constructor called: 15 false
Constructor called: 30 false
Constructor called: 15 false
Constructor called: 15 false
Constructor called: 10 false
Constructor called: 10 false
Constructor called: 3 false
Constructor called: 3 false
Constructor called: 5 false
Constructor called: 5 false
Constructor called: 45 false
Constructor called: 30 false
Constructor called: 15 false
I am now at Hudson version 1.323 and still seeing the warnings. the current
bundled log4j jar file is at version 1.2.9.
would it be possible to upgrade to 1.2.12? the latest stable version for log4j
is 1.5.8 but I am not sure if it will introduce breaking changes.
I had some similar issues with Hibernate 4, which uses jboss-logging, which also depends on a newer version of log4j.
So I opened a PR for this - https://github.com/jenkinsci/jenkins/pull/1734
The old version of log4j was pulled in by
<groupId>org.acegisecurity</groupId>
<artifactId>acegi-security</artifactId>
as a runtime dependency, so I just added an explicit compile dependency to the latest log4j version (1.2.17).
Thoughts on this?