ctubbsii commented on issue #3771: URL: https://github.com/apache/logging-log4j2/issues/3771#issuecomment-3301001966
I don't think the warning is friendly enough. I want to completely ignore the GraalVmProcessor... I don't need it (it's not common). I just want the PluginProcessor to generate the Log4j2Plugins.dat for my custom AbstractAppender implementation. Previously, this worked just fine by placing the log4j-core on the annotation processor path. Unfortunately, this new GraalVmProcessor has these noisy warnings, and that kills my build, because I run with 0 warnings. It's not clear how to disable this processor, unless I explicitly enumerate all the processors I want to use, just to implicitly exclude this one that I don't want. Ideally, if the prerequisite options don't exist, the processor doesn't run. It shouldn't just spit out warnings for everybody who doesn't want this processor. (Also, a bit of a complaint about the Log4j2Plugins.dat... I really wish log4j had gone with the Java ServiceLoader, and standard META-INF/services/ files like slf4j did, then I wouldn't have to rely on the log4j annotation processor to create the file.) -- 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]
