[
https://issues.apache.org/jira/browse/JENA-1185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15298272#comment-15298272
]
Andy Seaborne edited comment on JENA-1185 at 5/24/16 2:44 PM:
--------------------------------------------------------------
Thank you. That explains and the fixes should be complete. The directly
complaining about log4j is because Fuseki sets up slf4j over log4j itself
inside the webapp and the war is independent of Tomcat logging.
The changes will be in the next development build. However, some significant
changes (unrelated) have gone in since 3.1.0 so the development build is not as
tested as the last release.
A workaround is to add:
{noformat}
WEB-INF/lib/log4j-1.2.17.jar
WEB-INF/lib/slf4j-log4j12-1.7.21.jar
{noformat}
The first should stop the error; the second means that logging will be output
as before.
was (Author: andy.seaborne):
Thank you. That explains and the fixes should be complete. The directly
complaining about log4j is because Fuseki sets up slf4j over log4j itself
inside the webapp and the war is independent of Tomcat logging.
> log4j jar missing from fuseki-2.4.0.war
> ---------------------------------------
>
> Key: JENA-1185
> URL: https://issues.apache.org/jira/browse/JENA-1185
> Project: Apache Jena
> Issue Type: Bug
> Components: Fuseki
> Affects Versions: Fuseki 2.4.0
> Environment: Tomcat 8.0.35
> Reporter: Code Ferret
> Assignee: Andy Seaborne
> Fix For: Jena 3.1.1
>
>
> dowloaded
> http://apache.claz.org/jena/binaries/apache-jena-fuseki-2.4.0.tar.gz from
> https://jena.apache.org/download/index.cgi.
> Dropped fuseki.war into tomcat 8.0.35 and got:
> java.lang.NoClassDefFoundError: org/apache/log4j/helpers/Loader
> problem appears to be resolvable by including log4j-1.2.17.jar or similar in
> war file.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
