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
Bring JBossNettyLoggerFactory implementation in line with other implementations #27653
Conversation
…mentations This change essentially makes all the method implementations behave in the same way Netty's built-in implementations do. Fixes: quarkusio#27605 Co-authored-by: David M. Lloyd <david.lloyd@redhat.com>
log.error(msg, t); | ||
} | ||
|
||
} | ||
|
||
// MessageFormatter class copied from Netty because its methods are package private |
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.
😩 Can we also put in an enhancement request upstream to Netty to make these public? Otherwise it defeats the purpose of having the logger be pluggable after all.
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.
Yup: netty/netty#12761
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.
Once netty/netty#12763 is in and we have new Netty version (looks like 4.1.81
) in Quarkus that makes the methods public, we can delete the copied code
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.
#28126 now removes the copied code
MessageFormatter and FormattingTuple were originally copied from Netty because they didn't have the proper access modifiers for us to use them. With Netty 4.1.81 now being used in Quarkus, we can now use the actual classes so let's get rid of the redundancy. Follows up on: quarkusio#27653, quarkusio#28077
MessageFormatter and FormattingTuple were originally copied from Netty because they didn't have the proper access modifiers for us to use them. With Netty 4.1.81 now being used in Quarkus, we can now use the actual classes so let's get rid of the redundancy. Follows up on: quarkusio#27653, quarkusio#28077
MessageFormatter and FormattingTuple were originally copied from Netty because they didn't have the proper access modifiers for us to use them. With Netty 4.1.81 now being used in Quarkus, we can now use the actual classes so let's get rid of the redundancy. Follows up on: quarkusio#27653, quarkusio#28077
MessageFormatter and FormattingTuple were originally copied from Netty because they didn't have the proper access modifiers for us to use them. With Netty 4.1.81 now being used in Quarkus, we can now use the actual classes so let's get rid of the redundancy. Follows up on: quarkusio#27653, quarkusio#28077
MessageFormatter and FormattingTuple were originally copied from Netty because they didn't have the proper access modifiers for us to use them. With Netty 4.1.81 now being used in Quarkus, we can now use the actual classes so let's get rid of the redundancy. Follows up on: quarkusio#27653, quarkusio#28077
MessageFormatter and FormattingTuple were originally copied from Netty because they didn't have the proper access modifiers for us to use them. With Netty 4.1.81 now being used in Quarkus, we can now use the actual classes so let's get rid of the redundancy. Follows up on: quarkusio#27653, quarkusio#28077
This change essentially makes all the method implementations behave in the same
way Netty's built-in implementations do.
Fixes: #27605