[ 
https://issues.apache.org/jira/browse/LOG4J2-778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

SIBISH BASHEER updated LOG4J2-778:
----------------------------------

    Description: 
Hi log4j2 Team,

If you remember, i had developed a custom logger for splunk based on log4j2 
with the log4j2 team's help and had presented to my architects. Unfortunately 
the decision from the architects was not to use log4j2 because of the reason 
that log4j main author recommends logback not log4j2.

Have you heard of any such statements and if there is any scenario where 
logback is better than log4j2?

Thanks
Sibish

  was:
Hi log4j2 Team,

If you remember, i had developed a custom logger for splunk based on log4j2 and 
had presented to my architects. Unfortunately they have shot down log4j2 with a 
weird reason that log4j author recommended logback than log4j2.

Do you have any idea where such a strong opinion is coming from? And what 
response i should be giving. Also who exactly is the key author of log4j and 
logback? Is he the same?

Thanks
Sibish


> logback better than log4j2 as per log4j author
> ----------------------------------------------
>
>                 Key: LOG4J2-778
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-778
>             Project: Log4j 2
>          Issue Type: Question
>            Reporter: SIBISH BASHEER
>              Labels: log4j, logback
>
> Hi log4j2 Team,
> If you remember, i had developed a custom logger for splunk based on log4j2 
> with the log4j2 team's help and had presented to my architects. Unfortunately 
> the decision from the architects was not to use log4j2 because of the reason 
> that log4j main author recommends logback not log4j2.
> Have you heard of any such statements and if there is any scenario where 
> logback is better than log4j2?
> Thanks
> Sibish



--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to