JVM logging systems configured by classpath scanning are evil. That is all.
I was always annoyed by JVM loggers which offered multiple different ways to configure them: code, classpath, params, config file, each method silently overriding another... maybe. The only killer feature of my (unreleased) logging library is that its configuration is explicit.
-
-
Log4j2 is my most hated because it has a JSON configuration format that people often use, but it isn't documented and you're just expected to be able to translate from the XML syntax in your head
-
As an alternative I really like https://github.com/outr/scribe
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.