Github user jvz commented on the issue:
https://github.com/apache/zookeeper/pull/148
If any transitive dependencies rely on the log4j 1.x API itself (not SLF4J
or Commons Log or java.util.logging or an obscure bridge I didn't mention),
then they can be replaced with log4j-1.2-api from Log4j2 in general unless
they're defining custom appenders or other plugins. I'm not too familiar with
Ivy, but here's what Gradle generates in its embedded ivy.xml for something
similar:
```xml
<dependencies>
<dependency org="org.springframework.boot"
name="spring-boot-starter-log4j2" rev="" conf="compile->default">
<exclude org="commons-logging" module="commons-logging" name="*"
type="*" ext="*" conf="compile" matcher="exact"/>
<exclude org="com.google.code.findbugs" module="annotations" name="*"
type="*" ext="*" conf="compile" matcher="exact"/>
</dependency>
</dependencies>
```
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
