You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Mapping custom log levels to a default level (whether DEBUG, INFO or other) breaks tool chains in complex projects. With DEBUG as default, production environments are forced to that level of logging for some packages, when the custom log levels cannot be avoided.
Some SPI handling or even manual introduction of custom log levels could improve the behavior of the LevelTranslator for such cases.
The text was updated successfully, but these errors were encountered:
My apologies for just now seeing this. I've got no idea how I haven't noticed this in nearly a full year.
If it's not way too late, can you give an example of how you create custom levels? This project is typically used in WildFly and JBoss EAP where custom levels are not supported.
Mapping custom log levels to a default level (whether DEBUG, INFO or other) breaks tool chains in complex projects. With DEBUG as default, production environments are forced to that level of logging for some packages, when the custom log levels cannot be avoided.
Some SPI handling or even manual introduction of custom log levels could improve the behavior of the LevelTranslator for such cases.
The text was updated successfully, but these errors were encountered: