-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
log4j 1.2.17 in mvn dependency:tree, upgrade Jena version #52
Comments
Jena 4.3.2 is available now: <dependency>
<groupId>org.apache.jena</groupId>
<artifactId>apache-jena-libs</artifactId>
<version>4.3.2</version>
<type>pom</type>
</dependency> It doesn't list a dependency on log4j anymore:
However this leads to the following errors on
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
LodView has a transitive dependency on log4j 1.2.17 included from Apache Jena 2.13.0, see below.
According to https://logging.apache.org/log4j/1.2/:
However it is very important to not use a Jena version that depends on Log4j 2 < 2.15.0, as this suffers from an arguably even worse security vulnerability, see https://logging.apache.org/log4j/2.x/index.html.
The current latest version depends on log4j2 2.14.1. Thus, this current version should thus not be used:
However according to https://github.com/apache/jena/commits/jena-4.3.1, this seems to be fixed in Jena 4.3.1. Thus I will not create a pull request just yet and recommend waiting until Jena 4.3.1 is officially released and available on Maven central and then using that if it doesn't break anything.
The text was updated successfully, but these errors were encountered: