If you remove the log4j 1.x jar and replace it with the log4j-1.2-api jar from log4j 2 you will pass your security scans as Log4j 1 will no longer be present. But your application code can continue to use the Log4j 1 api when making logging calls. That said, converting the code to use the Log4j 2 API isn’t a bad thing as it is much better but only do it if you have to touch the code anyway.
Ralph > On Feb 19, 2020, at 8:27 AM, EDMONDO SENA <edse...@gmail.com> wrote: > > No Ralph because for security problem we have to pass to Log4j2. > Log4j1 will be out. > > > On 2020/02/19 15:20:44, Ralph Goers <ralph.go...@dslextreme.com> wrote: >> I you have code that is using Log4j 1’s Category class and don’t want to >> change it then just leave it alone and use the log4j-1.2-api jar to provide >> compatibility for those classes. >> >> Ralph >> >>> On Feb 19, 2020, at 7:41 AM, EDMONDO SENA <edse...@gmail.com> wrote: >>> >>> Hi Everybody, >>> >>> org.apache.log4j.Category is not available in Log4j2. >>> >>> How can we use it in Log4j2? >>> Must we change all our code? >>> Can you tell me as implement it in Log4j2? >>> >>> Kind regards. >>> //Edmondo. >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org >>> For additional commands, e-mail: log4j-user-h...@logging.apache.org >>> >>> >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org >> For additional commands, e-mail: log4j-user-h...@logging.apache.org >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org > For additional commands, e-mail: log4j-user-h...@logging.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-user-h...@logging.apache.org
