Github user lewismc commented on a diff in the pull request:
https://github.com/apache/jena/pull/474#discussion_r222382699
--- Diff: jena-jdbc/jena-jdbc-core/pom.xml ---
@@ -39,17 +39,28 @@
<version>3.10.0-SNAPSHOT</version>
</dependency>
- <!-- Jena Driver configures Log4j directly -->
- <dependency>
- <groupId>org.slf4j</groupId>
- <artifactId>slf4j-log4j12</artifactId>
- </dependency>
+ <!-- Jena Driver configures Log4j directly -->
+ <dependency>
+ <groupId>org.slf4j</groupId>
+ <artifactId>slf4j-log4j12</artifactId>
+ </dependency>
+
+ <dependency>
+ <groupId>log4j</groupId>
+ <artifactId>log4j</artifactId>
+ </dependency>
+
+ <dependency>
+ <groupId>org.apache.logging.log4j</groupId>
+ <artifactId>log4j-api</artifactId>
+ </dependency>
+
+ <!-- Intercept direct use of log4j2 -->
+ <dependency>
+ <groupId>org.apache.logging.log4j</groupId>
--- End diff --
Agreed. This is the behavior I get as well.
My thinking was that the dependency needed to be available at compile time
as oppose to only runtime... but maybe this thinking is wrong.
The generated Javadoc look fine but the error prevents a stable build.
---
