[
https://issues.apache.org/jira/browse/CLOUDSTACK-9158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15055622#comment-15055622
]
ASF GitHub Bot commented on CLOUDSTACK-9158:
--------------------------------------------
Github user miguelaferreira commented on the pull request:
https://github.com/apache/cloudstack/pull/1236#issuecomment-164376707
@borisroman slf4j sits in a layer above log4j. I?m not sure about the
particular case you are dealing with, however if we were using slf4j with log4j
consistently it would be much easier to now move to logback (the successor of
log4j). In thta case the code would be depending on the slf4j classes, and the
implementation would be configurable (i.g. log4j, logback, other logging libs).
> Remove SLF4J
> ------------
>
> Key: CLOUDSTACK-9158
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9158
> Project: CloudStack
> Issue Type: Sub-task
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Reporter: Boris Schrijver
> Assignee: Boris Schrijver
>
> We're using log4j everywhere in the project. Therefore SLF4J is abundant.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
