-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix the bug of ERROR StatusLogger Unrecognized format specifier when … #218
Conversation
…starting the jar package.
Hey @ASanny Any change you can make available for download a |
|
Amazing, thank you! I'm going to test this now and let you know. |
Confirmed, your patch fixes the logging! Thank you. I hope it's merged soon. |
@codefromthecrypt tagging you here in case you can review and merge this. |
sorry I was accidentally not watching.. looking now ;) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I haven't given it a spin but the explanation and configuration make sense to me.
@@ -80,6 +80,12 @@ | |||
<minimizeJar>true</minimizeJar> | |||
<filters> | |||
<!-- Prevent minification from excluding classes looked up by name --> | |||
<filter> | |||
<artifact>org.apache.logging.log4j:*</artifact> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Two blocks down it looks like we have log4j:log4j
. At some point I guess we switched dependencies and updating this part of the build was missed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yep must have been it!
3.1.1 on the way. thanks! |
When starting with a jar package, the following error log will appear:
After analysis, in the Maven Shade Plugin, if
<minimizeJar>
is set totrue
. The final generated jar file will be minimized. During the minimization process, a total of 163 classes related tolog4j2
will be removed:As a result, the pattern parser
org.apache.logging.log4j.core.pattern.PatternParser#createConverter
obtains the corresponding converter based onconverterId
to be null, resulting in the above error. The specific locations are as follows:The above bug can be fixed by including log4j related files in the final jar package: