[
https://issues.apache.org/jira/browse/CLOUDSTACK-10089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16178707#comment-16178707
]
Marc-Aurèle Brothier commented on CLOUDSTACK-10089:
---------------------------------------------------
100% in favor of log4j2 and the renaming of the logger variables. I tried a
branch earlier this year to move everything to slf4j, but the for example in
LogLevel class SLF4J doesn't offer the flexibility needed. Moreover in terms of
performance, log4j2 seems very good, better than logbak which would have been
the choice otherwise.
What would be nice also is to put in the PR tickets the bash commands used to
do the migrations (grep, awk, sed...). People might complain, but it's worth it.
> log4j version 1 is (beyond) end of life
> ----------------------------------------
>
> Key: CLOUDSTACK-10089
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10089
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Reporter: Daan Hoogland
> Assignee: Daan Hoogland
>
> maintenance and more flexible configuration and in addition and some new
> features like more advanced types of appenders make this upgrade lucrative,
> It is crosscutting and will leed to conflicts for many developers.
> (communication needed ;)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
