ppkarwasz commented on issue #1460: URL: https://github.com/apache/logging-log4j2/issues/1460#issuecomment-1536213772
@Chealer, Thanks for the remarks. Since we use Maven Site Plugin, we can replace the static [api-separation.md](https://github.com/apache/logging-log4j2/blob/2.x/src/site/markdown/manual/api-separation.md) file with a Velocity template and use the currently used version of all components. The version of all dependencies are kept as Maven POM properties. I agree that SLF4J 2.x should be the default one, although I wouldn't completely remove references to the 1.x series: it still has advantages, like out-of-the-box OSGI support without relying on the **optional** _Service Loader Mediator_. IMHO terms like "adapter", "bridge", "binding" (used in SLF4J 1.x), "provider" (used in SLF4J 2.x) and "implementation" are really confusing. If I want to connect X to Y I never remember if I should look for an "X bridge", "X adapter" or "X binding". I would rather use a single expression like "X to Y adapter" that clearly states that the component forwards API X calls to backend Y. I think we could we could start the example section with a graph representing all possible connections. This could roughly look like this with hyperlinks to the appropriate sections. | From | | | | To/From | | | | To | | | | --------------- | --- | ------------------- | --- | ----------------- | --- | ---------------- | --- | ------------------ | --- | ----------- | | **SLF4J 2.x** | → | `log4j-slf4j2-impl` | ↘ | | ↗ | → | → | **Log4j 2.x Core** | | | | **SLF4J 1.7.x** | → | `log4j-slf4j-impl` | → | **Log4j 2.x API** | → | `log4j-to-slf4j` | → | SLF4J | → | **Logback** | | **JUL** | → | `log4j-jul` | ↗ | | ↘ | `log4j-to-jul` | → | **JUL** | | | | **JCL** | → | `log4j-jcl` | ↗ | | | | | | | | | **JPL** | → | `log4j-jpl` | ↗ | | | | | | | | If someone wants to look into it, we love PRs. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
