[
https://issues.apache.org/jira/browse/ISIS-988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14260018#comment-14260018
]
Dan Haywood commented on ISIS-988:
----------------------------------
That ticket was implemented, meaning that we are mostly decoupled from log4j.
In particular, only the slf4j API is used for logging (except in some tests)
Where there is still a dependency is that Isis' currently hard-codes how it
configures log4j, this being in the IsisLoggingConfigurer class in the
isis-core-log4j module. That class is simply new'd up when Isis is
bootstrapped.
So, I think what this ticket really requires is for that hard-coded dependency
to be broken, such that the underlying logging mechanism be configured
according to the components on the classpath. Perhaps using the JDK6
ServiceLoader API could be used so that we could discover the
IsisLoggingConfigurer on the fly.
With that change made, it ought to be possible, just using Maven <exclusions>
tag, to bind slf4j to use log4j.
Do you want to experiment with decoupling IsisLoggingConfigurer?
> Upgrade to log4j 2
> -------------------
>
> Key: ISIS-988
> URL: https://issues.apache.org/jira/browse/ISIS-988
> Project: Isis
> Issue Type: Question
> Components: Core
> Reporter: Vladimir Nisevic
> Assignee: Dan Haywood
> Priority: Minor
>
> We are using Isis in combination with Elasticsearch ELK Stack
> (http://www.elasticsearch.org/overview/) where we send specific log events
> thru logging framework. Therefore it would be useful if we use log4j 2
> features like AsyncAppender, see e.g.
> http://www.infoq.com/news/2014/07/apache-log4j2
> Regs
> Vladimir
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
