glassfish
glassfish copied to clipboard
Abandon LogDomains loggers and use System.Logger
Why
- It is really hard to find something when half of logger names is obfuscated by LogDomains
- Prefer System.Logger (with GJULE as a backend, but could use any logging framework with some limitations)
- Current state is a growing mess (take a look on logging.properties).
- System.Logger is already preferred.
- Usages are more readable. Some usages are pretty ineffective, they deserve review.
How
It will be a lot of work, but quite easy. Most of changes could be probably done by Eclipse regexp finder.
- First do https://github.com/eclipse-ee4j/glassfish/issues/23627, don't start with this without that.
- Relates to #24064 and should be done before that.
- Bind logger names to the class name (standard)
- Simplify usages (no array construction required)
This issue has been marked as inactive and old and will be closed in 7 days if there is no further activity. If you want the issue to remain open please add a comment