-
Enhancement
-
Resolution: Done
-
Major
-
7.4.11.GA
In Java 9+ a System.Logger and System.LoggerFinder was introduced. The default dk.internal.logger.LoggerFinderLoader uses the ClassLoader.getSystemClassLoader() when attempting to find the System.LoggerFinder service. However, if a log manager is used, e.g. JBoss Log Manager, it's not likely on the system class path. If we use a custom LoggerFinder we could attempt to get a LoggerFinder from the log managers class loader.
- causes
-
MODULES-441 Lazily initialize System.Logger's in the ModuleLoggerFinder
- Resolved
- clones
-
MODULES-439 Create a delegating LoggerFinder
- Resolved
- is cloned by
-
JBEAP-25284 [GSS](8.0.z) MODULES-439 - Create a delegating LoggerFinder
- Closed
- is incorporated by
-
JBEAP-25285 [GSS](7.4.z) Upgrade JBoss Modules from 1.12.0.Final-redhat-00001 to 1.12.2.Final-redhat-00001
- Closed