Description
If Log4j plugins are implemented in the compiled source, and GraalVmProcessor arguments (-Alog4j.graalvm.groupId and -Alog4j.graalvm.artifactId) are not specified, then Log4j emits a warning:
TheGraalVmProcessorannotation processor is missing the recommendedlog4j.graalvm.groupIdandlog4j.graalvm.artifactIdoptions.
As warnings emitted by annotation processors themselves are independent of -Xlint, they cannot be suppressed; the obvious workaround would be to actually specify such arguments, but that rapidly backfires as soon as an incremental compilation doesn't include the plugin implementation, since the GraalVmProcessor is not activated and its arguments get unused, causing javac to emit a warning about unrecognized processor options (apparently, it's impossible to suppress annotation processor arguments too, alas), which disrupts compilations in strict linting mode (-Werror).
Proposed solution
The most straightforward, cheap solution, as suggested by @ppkarwasz, would be to lower the message severity, from WARNING to NOTE: that would keep its informative usefulness available for debugging investigation, while becoming friendly for regular usage — rather than adversarial, as it is now.
Configuration
Version: 2.26.1
Operating system: Ubuntu 24.04.4 LTS
JDK: OpenJDK version "17.0.19" 2026-04-21
Description
If Log4j plugins are implemented in the compiled source, and GraalVmProcessor arguments (
-Alog4j.graalvm.groupIdand-Alog4j.graalvm.artifactId) are not specified, then Log4j emits a warning:TheGraalVmProcessorannotation processor is missing the recommendedlog4j.graalvm.groupIdandlog4j.graalvm.artifactIdoptions.As warnings emitted by annotation processors themselves are independent of
-Xlint, they cannot be suppressed; the obvious workaround would be to actually specify such arguments, but that rapidly backfires as soon as an incremental compilation doesn't include the plugin implementation, since the GraalVmProcessor is not activated and its arguments get unused, causing javac to emit a warning about unrecognized processor options (apparently, it's impossible to suppress annotation processor arguments too, alas), which disrupts compilations in strict linting mode (-Werror).Proposed solution
The most straightforward, cheap solution, as suggested by @ppkarwasz, would be to lower the message severity, from
WARNINGtoNOTE: that would keep its informative usefulness available for debugging investigation, while becoming friendly for regular usage — rather than adversarial, as it is now.Configuration
Version: 2.26.1
Operating system: Ubuntu 24.04.4 LTS
JDK: OpenJDK version "17.0.19" 2026-04-21