If you are doing
Logger logger = LogManager.getLogger(“edu.nd.MyClass”);
or
Logger logger = LogManager.getLogger(edu.nd.MyClass.class);
then all you have to do is change the imports from org.apache.log4j to
org.apache.logging.log4j. Everything else would be optional.
If you are obtaining
Hi,
I'm upgrading an application from Log4j v1 to v2.
The v1 code often uses the debug()/info()/etc. methods with the
`Logger.debug(Object message, Throwable throwable)` signature to throw
errors while logging. In many cases, the `message` String is composed
using concatenation, as with
Hello Piotr,
So the solution for `ch.qos.logback:logback-core` would be to add this
dependency:
ch.qos.logback
logback-core
1.2.11
El mié, 30 mar 2022 a la(s) 02:42, Piotr P. Karwasz (piotr.karw...@gmail.com)
escribió:
> Hello Juan,
>
> On Tue, 29 Mar 2022 at 23:00, Juan Jose
[You are receiving this because you are subscribed to one or more user
or dev mailing list of an Apache Software Foundation project.]
ApacheCon draws participants at all levels to explore “Tomorrow’s
Technology Today” across 300+ Apache projects and their diverse
communities. ApacheCon showcases
Hello Pablo,
On Tue, 29 Mar 2022 at 19:58, Pablo Rogina wrote:
> However this warning appears (application launched with -Dlog4j2.debug=true):
> WARN StatusLogger Unable to load plugin class name
> com.mycompany.log4j.CustomAppender with key
> com.mycompany.log4j.customappender
This is an
Hello Juan,
On Tue, 29 Mar 2022 at 23:00, Juan Jose Silupú Maza
wrote:
> So, is my project affected by the LOG4J vulnerability? How do I mitigate it?
The Log4Shell vulnerability (CVE-2021-44228) concerned only the
`log4j-core` artifact developed by the Apache Logging Services
project. The
Nope, judging from the output you've shared, your project doesn't use Log4j
as a backend. `log4j-over-slf4j` simply forwards calls made to Log4j 1 API
to SLF4J.
On Tue, Mar 29, 2022 at 11:00 PM Juan Jose Silupú Maza <
juansilupum...@gmail.com> wrote:
> I have a maven project with spring-boot
