vy commented on PR #4041: URL: https://github.com/apache/logging-log4j2/pull/4041#issuecomment-4066217634
> I noticed this issue trying to build log4j2 with Bazel Would you mind elaborating on this a bit, please? Do you have an in-house Log4j build using Bazel? > Another option I was wondering about is whether it might be possible to move these processors to a separate maven submodule, to compile them separately before `log4j-core`, and avoid the need for the `maven-compiler-plugin` configuration that compiles in two phases. Do you think that's worth considering? That'd be a disruptive change. `PluginProcessor` users will need to adapt their class paths. Log4j 3 will have that modularity, but its release date is still uncertain. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
