Thanks Xander! I was also able to patch our version (dotCMS 5.2.1) based on the fix to the bug you shared here
This works much better, especially when you have custom logs defined in your Log4J config. (All of our plugins write to a separate log file so they don't get lost in dotcms.log.) When using class.getName() the Log4J rules don't work.
The patch contains two other classes not found in our dotCMS version that were required to compile it. Other than that it was pretty easy.
Nathan I. Keiter | Lead Network Applications Programmer | I.D.E.A Council Member
Gettysburg College | Information Technology | DataSystems
Campus Box 2453 | 300 North Washington Street | Gettysburg, PA 17325
> on behalf of Xander Steinmann <xan...@isaac.nl
Sent: Tuesday, May 4, 2021 10:00 AM
To: dotCMS User Group
Subject: [dotcms] Re: How to log in an OSGi plugin
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.