[
https://issues.apache.org/jira/browse/RATIS-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16963283#comment-16963283
]
Henrik Hegardt commented on RATIS-508:
--------------------------------------
[~szetszwo] I'm sorry, but I don't think the 002 patch was good and it breaks
ratis-examples and ratis-logservice's runtime. Because it is declared in
dependecyManagement it overrides the dependencies' transitive rules, thus
changing the result.
Just so I understand, why do you want log4j to be declared in the
dependencyManagement section?
> Switch from log4j to slf4j
> --------------------------
>
> Key: RATIS-508
> URL: https://issues.apache.org/jira/browse/RATIS-508
> Project: Ratis
> Issue Type: Improvement
> Components: common
> Affects Versions: 0.4.0
> Reporter: Hai Zhou
> Assignee: Henrik Hegardt
> Priority: Major
> Fix For: 0.5.0
>
> Attachments: RATIS-508.001.patch, RATIS-508.002.patch
>
>
> Improve the request to raise the abstraction level of our logging framework
> so that logging is done through slf4j instead of directly through log4j.
> This will allow users to swap-out the underlying logging framework, giving a
> choice of log4j, logback-classic, and log4j2.
> eg.
> In my project, I use logback, which conflicts with log4j.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
