-
-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Reevaluate the use of log4j within the deegree project #1248
Comments
List of logging APIs (incomplete):
|
Adding a chapter to the documentation how to swap the logging framework and how to build a WAR using an individual Maven POM shall be added. |
Log4j 1.2 has been reloaded into https://reload4j.qos.ch/ which provides an updated version of the old log4j 1.2 API. |
The TMC has the notion to move from Apache Log4j2 Version 2.x to logback as the default logging provider for the deegree 3.5 line. |
Given that we do not use most of the functionality of log4j we should discussing moving to a less complicated logging framework.
The text was updated successfully, but these errors were encountered: