This depends on which feature you want to work on. This ticket should really be an Epic with multiple associated Jira issues.
The easiest one would probably be to create a pattern converter that gets the module name similar to how the class name, method name and line number are captured. Next you could enhance the ExtendedThrowablePatternConverter to include module information. For that you just need to figure out how to capture the module information and inject it into the stack trace. For the ModuleLayerContextSelector you would want to look at the ClassLoaderContextSelector and modify it so that the LoggerContext is associated with the ModuleLayer the class belongs to instead of the ClassLoader. Ralph > On May 19, 2020, at 3:53 AM, Alex Orlov <[email protected]> wrote: > > > Hi all, > > I want to try to resolve this issue > https://issues.apache.org/jira/browse/LOG4J2-2464 > Could anyone provide instruction what I should do, as I know log4j2 > architecture very badly. > > I mean, something like this: > 1) Do this. > 2) Do that. > 3) Plug and pray. > > -- > Alex Orlov
