[
https://issues.apache.org/jira/browse/JENA-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17295986#comment-17295986
]
Andy Seaborne commented on JENA-1867:
-------------------------------------
Small problem:
AbstractJenaDriverTests.driver_connect_bad_06 no longer throws an exception
org.apache.jena.jdbc.mem.TestMemDriver.driver_connect_bad_06
org.apache.jena.jdbc.remote.TestRemoteEndpointDriver.driver_connect_bad_06
org.apache.jena.jdbc.tdb.TestJenaJdbcTdbDriver.driver_connect_bad_06
The test looks irrelevant now.
I have some cleanup (suppress logging, fix warnings) to make release handling
easier- I can include that change in the PR.
> Move jena-jdbc off log4j1
> -------------------------
>
> Key: JENA-1867
> URL: https://issues.apache.org/jira/browse/JENA-1867
> Project: Apache Jena
> Issue Type: Task
> Components: JDBC
> Affects Versions: Jena 3.14.0
> Reporter: Andy Seaborne
> Priority: Minor
>
> 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:
> # Bundle log4j2; possibly use {{LogCtl}} rather than code directly.
> # Remove it (is it documented outside javadoc?)
> # 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
