ppkarwasz opened a new issue, #2131: URL: https://github.com/apache/logging-log4j2/issues/2131
There are a couple of CLI commands in the current 2.x artifacts. Their code is not used by other Log4j components. ### `log4j-1.2-api` `log4j-1.2-api` contains a [Log4j1ConfigurationConverter](https://github.com/apache/logging-log4j2/blob/2.x/log4j-1.2-api/src/main/java/org/apache/log4j/config/Log4j1ConfigurationConverter.java), which shares code with the old (and **disabled**) [`Log4j1ConfigurationFactory`](https://github.com/apache/logging-log4j2/blob/2.x/log4j-1.2-api/src/main/java/org/apache/log4j/config/Log4j1ConfigurationFactory.java). IMHO: - both components and their dependencies should be removed in 3.x, - their functionality should be moved to a separate component (in a new repo or `logging-log4j-transform`). Remark that the new configuration factory used by `log4j-1.2-api` is based on [`org.apache.log4j.builders`](https://github.com/apache/logging-log4j2/tree/2.x/log4j-1.2-api/src/main/java/org/apache/log4j/builders) and is extensible. With some minor adjustments to the `o.a.l.b.Builder` interface we can switch `Log4j1ConfigurationConverter` to the new infrastructure and use it in openrewrite/rewrite-logging-frameworks#48. ### `log4j-core` Log4j Core contains a simple custom logger generator and an old copy of [remkop/picocli](https://github.com/remkop/picocli). This should also be removed from the main code and transfered to a new artifact. -- 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: notifications-unsubscr...@logging.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
