Closed GoogleCodeExporter closed 9 years ago
The cause of this issue is that the Jenkins webapp currently includes log4j
v1.29, because it is a dependency of acegisecurity v1.0.7.
And that Jenkins has no log4j.properties or log4j.xml files anywhere, to
configure log4j.
And that the monitoring plugin has seen that log4j classes are found, so it
logs a few messages with log4j.
So log4j warns about the missing configuration.
Perhaps Jenkins should include a default log4j.xml for libraries
(acegisecurity) and plugins, which would want to log with log4j. A particular
plugin should probably not include log4j.xml itself.
Anyway, this is just a warning about log4j configuration and it does no harm to
Jenkins or to the plugin. So resolving as won't fix.
Original comment by evernat@free.fr
on 19 Dec 2013 at 4:58
Original issue reported on code.google.com by
npfist...@picturesafe.de
on 28 Nov 2013 at 10:11