i-pk-pjers-i

Hi, Yes, it includes log4j2.xml - log4j2 does attempt to read the log4j2.xml file which is why it throws a warning/error when trying to read the PatternLayout pattern element. I do have keep class for all of the libraries like disruptor and log4j2. Cheers.

Hi, If you're replying to my comment, I posted a picture of my issue, as well as the exact configuration of log4j2.xml as well as my ProGuard configuration. The log4j2.xml seems like it is being read properly, which is why it detects that there is a PatternLayout tag. You can see the log4j2.xml exists in the jar here: https://i.imgur.com/eoRjDLU.png Cheers.

I'm still having issues with this even with 6.2.1. I get this lovely output in my console: https://i.imgur.com/kihYzjY.png 2019-12-07 20:00:51,156 main ERROR PatternLayout contains an invalid element or attribute "pattern" when an obfuscated application attempts to read my log4j2.xml file: https://pastebin.com/C0hQkTMY - even though the logger.error("Yes") still prints to the console, as you can see in the picture I linked - it's missing my custom pattern for date/time. Here is my ProGuard configuration:...

I'm still having issues with this even with 6.2.1. I get this lovely output in my console: https://i.imgur.com/kihYzjY.png 2019-12-07 20:00:51,156 main ERROR PatternLayout contains an invalid element or attribute "pattern" when an obfuscated application attempts to read my log4j2.xml file: https://pastebin.com/C0hQkTMY - even though the logger.error("Yes") still prints to the console, as you can see in the picture I linked - it's missing my custom pattern for date/time. Here is my ProGuard configuration:...

I'm still having issues with this even with 6.2.1. I get this lovely output in my console: https://i.imgur.com/kihYzjY.png 2019-12-07 20:00:51,156 main ERROR PatternLayout contains an invalid element or attribute "pattern" when an obfuscated application attempts to read my log4j2.xml file: https://pastebin.com/C0hQkTMY - even though the logger.error("Yes") still prints to the console, as you can see in the picture I linked - it's missing my custom pattern for date/time. Here is my ProGuard configuration:...

Hi, Are there any plans to support multi-release jars in the future? I think they are the best option going forward. I tried using the latest log4j2 as an injar on it's own, as a part of my main injar, and as a library jar, all with the proper filter. None of them worked and the warning was still produced. Thanks.

Hi, Yeah, I think I understand now. I'm glad to hear it will be fixed in the future. Thanks.

Hi, Sorry, I'm not quite sure I understand. Is this something that can and possibly will be fixed - so that when I backup the configuration file it will still retain the checkmark and the specific classes I want filled out in the textbox after importing the configuration file? The way it functions right now, I have to manually enter those and select the checkbox for it to function the way I expect (and want) it to. It's not a huge deal to me, but it is an extra step that I'd rather not have to take...