GitHub user ppkarwasz added a comment to the discussion: java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId` options
The warning in the release notes warning is a simplified explanation of the actual behavior. The `GraalVmProcessor` will only produce an error out when **both** of the following are true: 1. **Your code includes at least one Log4j Core Plugin** (i.e., you have a class annotated with `@Plugin`). 2. You **did not** supply the required compiler arguments: ``` -Alog4j.graalvm.groupId=<your.groupId> -Alog4j.graalvm.artifactId=<your.artifactId> ``` I tested this locally (using `javac` in both single- and multi-module Maven setups) without any issues—no errors appeared when no `@Plugin` was present. Can you share a snippet or small test project where the issue does occur? GitHub link: https://github.com/apache/logging-log4j2/discussions/3755#discussioncomment-13511583 ---- This is an automatically sent email for dev@logging.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@logging.apache.org
