Consider making plugin builds less chatty

[snicoll]

Our build has custom plugins and this is the output we have on a regular Gradle build:

Note: GraalVmProcessor: writing GraalVM metadata for 12 Java classes to `META-INF/native-image/log4j-generated/org.springframework.boot/spring-boot-log4j/reflect-config.json`.
Note: PluginProcessor: writing plugin descriptor for 13 Log4j Plugins to `META-INF/org/apache/logging/log4j/core/config/plugins/Log4j2Plugins.dat`.

One thing that always tricks me is that I often forgets it is about log4j, especially reading "Note: GraalVmProcessor: writing GraalVM metadata for 12 Java classes".

Can you please consider this to be less chatty? Do we really need that log by default? If we really do, can't we do something to make it a bit more obvious that it is log4j doing something during the build? Thank you

[ramanathan1504]

@snicoll,

Thanks for raising this issue. You are completely right—the build logs are too chatty and the GraalVmProcessor message lacks [Log4j] branding, making its origin ambiguous.

Current Workaround

As documented in our Plugin Documentation, Log4j provides an option to suppress processor notes by raising the minimum allowed log level to WARNING:

For Gradle (build.gradle):

compileJava {
    options.compilerArgs << '-Alog4j.plugin.processor.minAllowedMessageKind=WARNING'
}

For Maven (pom.xml):

<plugin>
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-compiler-plugin</artifactId>
    <configuration>
        <compilerArgs>
            <arg>-Alog4j.plugin.processor.minAllowedMessageKind=WARNING</arg>
        </compilerArgs>
    </configuration>
</plugin>

---

Known Gap & Upcoming Fix

While investigating this, we identified two gaps:

1. GraalVmProcessor ignores this option: While PluginProcessor goes silent with the option above, GraalVmProcessor currently lacks this check and still prints its note.
2. Missing [Log4j] Prefix: The log messages do not explicitly mention Log4j.

Fix Plan:

• Update GraalVmProcessor to respect log4j.plugin.processor.minAllowedMessageKind.
• Prefix all processor log messages with [Log4j] (e.g., [Log4j] GraalVmProcessor: ...).

---

If you are interested in contributing, we would love a Pull Request for this!

The PR should include:

• The fix in GraalVmProcessor and updated message prefixes in both processors.
• A unit/integration test verifying the behavior.
• A changelog entry under src/changelog/.

Thanks