[JENA-1867] Move jena-jdbc off log4j1

• Type: Task
• Status: Closed
• Priority: Minor
• Resolution: Done
• Affects Version/s: Jena 3.14.0
• Fix Version/s: Jena 4.0.0
• Component/s: JDBC
• Assignee: Rob Vesse
• Reporter: Andy Seaborne
• Created: 20/Mar/20 15:08
• Updated: 01/Apr/21 09:21
• Resolved: 08/Mar/21 12:41

Description

Now that JENA-1005 has been completed, the only part of Jena directly mentioning log4j1 is jena-jdbc. This controls log4j1 directly.

{org.apache.jena.jdbc.JnaDriver}} and TestMemDriverWithLogging.

The dependency on log4j1 is managed in jena-jdbc/pom.xml to isolate it from the rest of Jena and used in jena-jdbc-core/pom.xml.

Possibilities include:

1. Bundle log4j2; possibly use LogCtl rather than code directly.
2. Remove it (is it documented outside javadoc?)
3. Continue with log4j1 can record the fact for the automated GH security scan of dependencies.

(2) is motivated by my lack of knowledge about how visible the feature is and whether such "logging less" use case arise nowadays.

Issue Links

• relates to: JENA-1005 Move off Log4j v1.
• links to: GitHub Pull Request #946