Am 17.12.19 um 20:36 schrieb Ceki:
Yes, there is still time to make changes.
One other thing: I keep conflating Bridges, Adapters, and am never quite sure whether some Log4J bridge is SLF4J is getting data from, or sending data to. It's also a major pain point whenever I explain SLF4J to somebody. (It doesn't help that the .jars use yet another terminology, just as log4j-over-slf4j. Hey, I probably got that name wrong, which even reinforces my point.) Suggestion: Call these things "Frontend" and "Backend". An SLF4J Frontend is the API that SLF4J is presenting to callers. So... the Log4j frontend would be the library that provides the Log4j API and routes the calls to SLF4J. A Log4j backend is the thing that SLF4J calls to emit log messages. Jar/artifact names could be something like - log4j-frontend-for-slf4j - slf4j-backend-to-log4j which also reflects the direction of the data flow (caller to the left, callee to the right). The names are a bit clunky and ugly, but then you mention them only once in your buildfiles, so that's not a big thing. Regards, Jo