[
https://issues.apache.org/jira/browse/JENA-1220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15407536#comment-15407536
]
ASF subversion and git services commented on JENA-1220:
-------------------------------------------------------
Commit e2a1bd5ebbf886a7a45c9697c7688f6ad1ead099 in jena's branch
refs/heads/master from [~andy.seaborne]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=e2a1bd5 ]
JENA-1220: Set logging (if not already set) before Jena to avoid log4j warning.
> Fuseki logging setup
> --------------------
>
> Key: JENA-1220
> URL: https://issues.apache.org/jira/browse/JENA-1220
> Project: Apache Jena
> Issue Type: Improvement
> Components: Fuseki
> Affects Versions: Fuseki 2.4.0
> Reporter: Andy Seaborne
> Assignee: Andy Seaborne
> Priority: Minor
> Fix For: Fuseki 2.4.1
>
>
> Improve the logging setting so that:
> Take logging setup out of initialization of the Fuseki code system
> Logging is set by the standalone server in the command line setup. Then
> ensure logging is in {{FusekiServerEnvironmentInit}}, the
> ServletContextListener which is where it is triggered for the WAR file if the
> webapp container has not already set it up.
> If using Fuseki without the webapp, i.e. in an embedded mode, do not set
> logging and rely on the application to have set slf4j along with the rest of
> Jena.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
