jmeter-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [Bug 60589] Migrating LogKit to SLF4J - Drop avalon, logkit and excalibur with backward compatibility for 3rd party modules.
Date Sun, 15 Jan 2017 16:54:12 GMT

--- Comment #1 from Woonsan Ko <> ---
My solution ideas (roughly):
- can determine (default) log4j2 configuration file location
(e.g, first ./log4j2.xml, second bin/log4j2.xml) if log4j2 configuration system
property is not explicitly set by users.
- Add jcl-over-slf4j jar and Log4j 2's log4j-1.2-api.jar dependencies for
Commons Logging and Log4j using libraries.
- Remove logkit, excalibur and avalon dependencies.
- Fork logkit Logger interface with a wrapper class for slf4j logger for
backward compatibility in jorphan. So we can remove logkit dependencies in
maven pom as well.
- Change LoggingManager only for using wrappers for slf4j. Drop logging
- Remove all the logging related JMeter configuration properties and command
line arguments support.
- Provide logging event listener for the Logs Viewer UI feature).
  (This can be a log4j2 listener implementation since I don't see any listener
support by slf4j itself (yet).)

You are receiving this mail because:
You are the assignee for the bug.
View raw message