doc: Clarify and enhance GraalVmProcessor
configuration example
#3786
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This update refines the
GraalVmProcessor
configuration example in response to feedback from #3755. The goal is to make the example more reliable and aligned with common Maven project setups. Key improvements include:Ensuring consistent parameter usage: The example now adds
-Alog4j.graalvm.groupId
and-Alog4j.graalvm.artifactId
to all executions of the Maven Compiler Plugin. This guarantees correct behavior regardless of the execution ID used in user projects.Simplifying plugin execution setup: Instead of introducing a dedicated
generate-log4j-plugin-descriptor
execution, the example now modifies the existingdefault-compile
execution. This reflects the most typical use case, where annotation processing and compilation occur together.These changes aim to make the setup easier to adopt while reducing configuration errors.