[
https://issues.apache.org/jira/browse/LOG4J2-1926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Kalnichevski closed LOG4J2-1926.
-
Android static code analyzer no longer chokes on log4j-api. Tested with the
latest 2.8.3
[
https://issues.apache.org/jira/browse/LOG4J2-1926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16032657#comment-16032657
]
Oleg Kalnichevski commented on LOG4J2-1926:
---
Remko,
The real question to m
[
https://issues.apache.org/jira/browse/LOG4J2-1926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16032568#comment-16032568
]
Oleg Kalnichevski commented on LOG4J2-
that
> the user
> logs String messages only. I personally think that was a design
> mistake, if
> only for the fact that a String-based API prevents garbage-free
> logging.
> The Message implementations simply cover a range of common use cases.
>
> Remko
>
>
> O
decision or it simply happened.
After having taken a cursory look at Log4j2 APIs I must admit I am bit
unpleasantly surprised at how heavy they feel. For instance, was it
really necessary to put all sort of concrete Message implementations
into what is meant to be an abstract logging API?
Ol
Folks,
I did try to do a reasonable research on the matter prior to posting my
question here, nevertheless, please do excuse me if I am asking
something obvious or well documented somewhere (in a place I was unable
to find).
I read that people had been more or less successfully using Log4j2 2.3
o
