Heh, good that it's fixed in any case. I've linked to that issue in the
issue I created, and closed it. Thanks, Carter.
On Thu, Jan 20, 2022 at 12:39 PM Carter Kozak wrote:
> Ah! I hadn’t been able to recall where this was reported, but I fixed it
> on Monday as LOG4J2-3345 :-)
>
> -ck
>
> > On
Ah! I hadn’t been able to recall where this was reported, but I fixed it on
Monday as LOG4J2-3345 :-)
-ck
> On Jan 20, 2022, at 03:57, Travis Spencer wrote:
>
> Added a ticket with a sample project attached which reproduces the issue:
> https://issues.apache.org/jira/browse/LOG4J2-3355
>
>>
Added a ticket with a sample project attached which reproduces the issue:
https://issues.apache.org/jira/browse/LOG4J2-3355
On Fri, Jan 7, 2022 at 1:38 PM Gary Gregory wrote:
> If our code changes, please add a code comment that explains why that class
> is used so that maintenance is easier in
If our code changes, please add a code comment that explains why that class
is used so that maintenance is easier in the future :-)
Gary
On Fri, Jan 7, 2022, 07:21 Volkan Yazıcı wrote:
> Thanks for reaching out, Travis! I don't have much of an experience in
> log4j-jpl, but after a 15min check
Thanks for reaching out, Travis! I don't have much of an experience in
log4j-jpl, but after a 15min check, this definitely seems like a bug to me.
(`MessageFormatMessage` should have been used instead of
`ParametrizedMessage`, I guess.) Mind filling in a JIRA ticket along with
your findings, please
