Re: [D] java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId` options [logging-log4j2]

[via GitHub]

GitHub user kwakeroni 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

I have the same issue.
The release notes say "the processor will fail the build if the required 
log4j.graalvm.groupId and log4j.graalvm.artifactId parameters are not 
provided", but according to this page: 
https://logging.apache.org/log4j/2.x/manual/plugins.html#plugin-registry the 
GraalVM stuff is optional.
I don't see an option to turn it off, though.

GitHub link: 
https://github.com/apache/logging-log4j2/discussions/3755#discussioncomment-13505114


This is an automatically sent email for dev@logging.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@logging.apache.org

Re: [D] java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId` options [logging-log4j2]

[via GitHub]

GitHub user ratoaq2 edited a discussion: java.lang.IllegalArgumentException: 
The `GraalVmProcessor` annotation processor is missing the required 
`log4j.graalvm.groupId` and `log4j.graalvm.artifactId` options

Hi all,

I have a java 21 maven project which uses eclipse compiler 
org.codehaus.plexus:plexus-compiler-eclipse:2.15.0 and  has a log4j plugin 
using a Log4j2Plugins.dat file and configured the compiler with:
```

  org.apache.maven.plugins
  maven-compiler-plugin
  

  generate-log4j-plugin-descriptor
  
compile
  
  process-classes
  
only

  
org.apache.logging.log4j
log4j-core
  


  
org.apache.logging.log4j.core.config.plugins.processor.PluginProcessor

  

  

```

After upgrading from 2.24.3 to 2.25.0 now my compilation is failing with:

```
19:43:54  [INFO] --- compiler:3.14.0:compile (default-compile) @ common ---
19:43:55  [INFO] Recompiling the module because of changed source code.
19:43:55  [INFO] Compiling with eclipse [debug deprecation parameters target 
21] to target/classes
19:43:55  [INFO] -
19:43:55  [ERROR] COMPILATION ERROR : 
19:43:55  [INFO] -
19:43:55  [ERROR] /redacted//redacted/src/main/redacted/Redacted.java: 
Internal compiler error: java.lang.Exception: 
java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor 
is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId` 
options.
19:43:55  The generation of GraalVM reflection metadata for your Log4j Plugins 
will be disabled. The generation of GraalVM reflection metadata for your Log4j 
Plugins will be disabled.
19:43:55  [ERROR] Unknown source: The `GraalVmProcessor` annotation processor 
is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId` 
options.
19:43:55  The generation of GraalVM reflection metadata for your Log4j Plugins 
will be disabled.
19:43:55  [INFO] 2 errors 
```

Is anyone facing similar issue? I tried to specify the graal processor with its 
arguments, but that doesn't work either.


GitHub link: https://github.com/apache/logging-log4j2/discussions/3755


This is an automatically sent email for dev@logging.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@logging.apache.org

Re: [D] java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId` options [logging-log4j2]

[via GitHub]

GitHub user THausherr 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

Same for me with Apache PDFBox. What I noticed is that it works when building 
the subproject, but not when building the whole project which includes the 
subproject.

GitHub link: 
https://github.com/apache/logging-log4j2/discussions/3755#discussioncomment-13510156


This is an automatically sent email for dev@logging.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@logging.apache.org

Re: [D] java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId` options [logging-log4j2]

[via GitHub]

GitHub user ftreede 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

It is automatically registered via META-INF services. So the only way to turn 
it off is to turn off all annotation processing.

It would be better if you'd have to explicitly enable it, I don't think it 
needs to be in the services if you specify it explicitly.

We will rollback and hold off on 2.25 until this is fixed.

GitHub link: 
https://github.com/apache/logging-log4j2/discussions/3755#discussioncomment-13509519


This is an automatically sent email for dev@logging.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@logging.apache.org

Re: [D] java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId` options [logging-log4j2]

[via GitHub]

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

Nice catch! :100:
Somehow `only` ended up in my example, which disables the 
compilation of classes. I edited the answer to fix it.



GitHub link: 
https://github.com/apache/logging-log4j2/discussions/3755#discussioncomment-13512543


This is an automatically sent email for dev@logging.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@logging.apache.org

Re: [D] java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId` options [logging-log4j2]

[via GitHub]

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

@THausherr,

I couldn't reproduce your problems with PDFBox. I submitted my changes as 
apache/pdfbox#207.

GitHub link: 
https://github.com/apache/logging-log4j2/discussions/3755#discussioncomment-13512863


This is an automatically sent email for dev@logging.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@logging.apache.org

Re: [D] java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId` options [logging-log4j2]

[via GitHub]

GitHub user ratoaq2 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 proc none didn't seem to work for me...

It seems I got it working with:
```xml


org.apache.logging.log4j
log4j-core
${log4j2.version}





```

GitHub link: 
https://github.com/apache/logging-log4j2/discussions/3755#discussioncomment-13512931


This is an automatically sent email for dev@logging.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@logging.apache.org

Re: [D] java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId` options [logging-log4j2]

[via GitHub]

GitHub user ratoaq2 edited a comment on the discussion: 
java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor 
is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId` 
options


It seems I got it working with proc none plus empty annotation processors:
```xml


org.apache.logging.log4j
log4j-core
${log4j2.version}





```

GitHub link: 
https://github.com/apache/logging-log4j2/discussions/3755#discussioncomment-13512931


This is an automatically sent email for dev@logging.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@logging.apache.org

Re: [D] java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId` options [logging-log4j2]

[via GitHub]

GitHub user ratoaq2 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

It seems a bit cumbersome for a project that has nothing to do with Graalvm

GitHub link: 
https://github.com/apache/logging-log4j2/discussions/3755#discussioncomment-13512957


This is an automatically sent email for dev@logging.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@logging.apache.org

Re: [D] java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId` options [logging-log4j2]

[via GitHub]

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=
   -Alog4j.graalvm.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

Re: [D] java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId` options [logging-log4j2]

[via GitHub]

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

Hi @kwakeroni,

There’s **no dedicated flag** to turn `GraalVmProcessor` off, since you can 
effectively control it through standard compiler options.

As @ftreede mentioned, since Java 6, `javac` has **automatically loaded** all 
annotation processors found on the annotation processor path (which, by 
default, is just the classpath). This implicit behavior has been flagged as a 
security concern and is now **deprecated as of Java 23** (see [this JDK 23 
heads-up](https://inside.java/2024/06/18/quality-heads-up/) and the [excellent 
write-up 
here](https://javapro.io/2024/11/19/discovering-the-perfect-java-supply-chain-attack-vector-and-how-it-got-fixed/)).

Keeping the spirit of the changes in JDK 23, we intentionally make 
`GraalVmProcessor` fail with an **`ERROR`** (instead of silently ignoring it or 
logging a warning) because:

* It helps developers become immediately aware that a new annotation processor 
is active.
* It forces an **explicit decision**: either configure it properly (opt-in) or 
disable it (opt-out).

### ✅ How to Opt-Out

Depending on whether you use **other annotation processors**, you can take one 
of two approaches:

 1. You **don’t** use other annotation processors

You can simply disable all annotation processing:

```xml

  org.apache.maven.plugins
  maven-compiler-plugin
  

none
  

```

 2. You **do** use other annotation processors

In this case, declare them explicitly and isolate your annotation processor 
classpath:

```xml

  org.apache.maven.plugins
  maven-compiler-plugin
  

  
  
org.apache.logging.log4j
log4j-core
2.25.0
  


  
  
org.apache.logging.log4j.core.config.plugins.processor.PluginProcessor

  

```

This ensures that only the processors you trust and need are loaded—nothing 
more, nothing less.

### ✅ How to Opt-In

An example on to use both `PluginProcessor` and `GraalVmProcessor` is available 
on the [documentation page you 
site](https://logging.apache.org/log4j/2.x/manual/plugins.html#plugin-registry)

GitHub link: 
https://github.com/apache/logging-log4j2/discussions/3755#discussioncomment-13512010


This is an automatically sent email for dev@logging.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@logging.apache.org

Re: [D] java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId` options [logging-log4j2]

[via GitHub]

GitHub user THausherr edited a comment on the discussion: 
java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor 
is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId` 
options

I tried the last change with default-compile and now the project that follows 
the problematic project claims that the previous package doesn't exist. I 
looked into the repository directory, the jar files are there, but much 
smaller. It turned out the class files are missing.

```

org.apache.maven.plugins
maven-compiler-plugin


default-compile

only


org.apache.logging.log4j
log4j-core
${log4j2.version}




org.apache.logging.log4j.core.config.plugins.processor.PluginProcessor

org.apache.logging.log4j.core.config.plugins.processor.GraalVmProcessor


-Alog4j.graalvm.groupId=${project.groupId}
-Alog4j.graalvm.artifactId=${project.artifactId}





```

GitHub link: 
https://github.com/apache/logging-log4j2/discussions/3755#discussioncomment-13512509


This is an automatically sent email for dev@logging.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@logging.apache.org

Re: [D] java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId` options [logging-log4j2]

[via GitHub]

GitHub user ppkarwasz edited a comment on the discussion: 
java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor 
is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId` 
options

Hi @ratoaq2,

Thanks for the detailed error log — it's very helpful.

>From what you've shared, the issue is occurring during the `default-compile` 
>Maven Compiler Plugin execution, not in the custom 
>`generate-log4j-plugin-descriptor` execution you configured. Specifically:

```
[INFO] --- compiler:3.14.0:compile (default-compile) @ common ---
[INFO] Compiling with eclipse [...] to target/classes
[ERROR] Internal compiler error: java.lang.IllegalArgumentException: 
The `GraalVmProcessor` annotation processor is missing the required 
`log4j.graalvm.groupId` and `log4j.graalvm.artifactId` options.
```

If you want to use a separate execution for annotation processing, you need to 
disable annotation processing in `default-compile`:

```xml

  default-compile
  
none
  

```

If, on the other hand, you want to perform both compilation and annotation 
processing (Log4j plugin descriptor + GraalVM metadata) **in a single Maven 
execution**, you can fully configure the `default-compile` phase like this:

```xml

  org.apache.maven.plugins
  maven-compiler-plugin
  3.14.0
  

  org.codehaus.plexus
  plexus-compiler-eclipse
  2.15.0

  
  

eclipse
21

none
  
  

  default-compile
  

  
org.apache.logging.log4j
log4j-core
2.25.0
  


  

org.apache.logging.log4j.core.config.plugins.processor.PluginProcessor
  
  

org.apache.logging.log4j.core.config.plugins.processor.GraalVmProcessor
  


  
  -Alog4j.graalvm.groupId=${project.groupId}
  -Alog4j.graalvm.artifactId=${project.artifactId}

  

  

```

I hope that helps solving your problem.


GitHub link: 
https://github.com/apache/logging-log4j2/discussions/3755#discussioncomment-13512223


This is an automatically sent email for dev@logging.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@logging.apache.org

Re: [D] java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId` options [logging-log4j2]

[via GitHub]

GitHub user THausherr 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

Thank you! It builds successfully now. I see you also made a (slightly 
different) PR, I'll have a look at it tomorrow.

GitHub link: 
https://github.com/apache/logging-log4j2/discussions/3755#discussioncomment-13513048


This is an automatically sent email for dev@logging.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@logging.apache.org

Re: Archiving Chainsaw and Flume GitHub repositories

[Matt Sicker]

I have a similar problem reviewing Log4j email. The flood of GitHub 
notifications makes it difficult to review anymore.

> On Jun 17, 2025, at 11:01, Ralph Goers  wrote:
> 
> I am actively working on Log4j-Audit at the moment. I am currently upgrading 
> it to all the latest dependencies.  Once I commit that I will be adding in 
> ElectronJS to solve the UI problem I have had with that. The upgrade only has 
> one challenging aspect - The upgrade of JGit necessitates that I replace JSch 
> with Apache Mina for SSH access to the Git repo. I have a need to use this to 
> add audit logging to some services at work so I need to get this done asap.  
> I will probably have issues here doing a release as I have no idea if I can 
> still publish the web site or perform a release given how the build process 
> has changed for the other log4j projects.
> 
> I do have a task to upgrade Flume as well as add a fix for a problem that was 
> reported. As you know we use Flume at my work and it needs to be upgraded. So 
> I will be jumping back on this in the next couple of months.
> 
> I don’t work on Chainsaw and never have. I don’t know of anyone who plans to 
> do any work on it so I do not object to archiving chainsaw.
> 
> I do have to apologize. While I try to follow the dev l& pmc lists I have had 
> a terrible time following the email generated by GitHub. I currently have 
> almost 10,000 unread messages from GitHub for the logging project. My 
> mailboxes for Maven are worse. I have 30,000 unread messages from Jira and 
> 11,000 from GitHub. I’ve given up trying to keep up to date with Maven’s 
> email.
> 
> Ralph
> 
>> On Jun 16, 2025, at 1:23 AM, Volkan Yazıcı  wrote:
>> 
>> Hey Ralph! In the last 6 months, I haven't noticed any progress regarding
>> these projects. Though you might have changes ready locally, or I might
>> have missed your activity. Would you mind updating us on your progress and
>> plans, please?
>> 
>> On Wed, Jan 15, 2025 at 2:21 PM Ralph Goers 
>> wrote:
>> 
>>> -1 on Flume
>>> 
>>> Despite you not seeing visible evidence I am still working on these. I am
>>> actually fairly confident I will need to create releases of Flume in the
>>> next 6 months.
>>> 
>>> Ralph
>>> 
 On Jan 15, 2025, at 2:05 AM, Volkan Yazıcı  wrote:
 
 Chainsaw and Flume projects have been moved to dormant state with PMC
 consensus. Yet their GitHub repositories (i.e., `logging-chainsaw` and
 `logging-flume*`) don't reflect this and they  weekly get flagged by
>>> GitHub
 due to vulnerable dependencies. This is also confusing for users, since
>>> the
 list of Logging Services dormant projects
  and the GitHub repository
 statuses don't match.
 
 *I suggest archiving¹ `logging-chainsaw` and `logging-flume*` GitHub
 repositories. Objections?*
 
 ¹ When a GitHub project gets archived, it becomes read-only. This is a
 reversible operation; we can anytime unarchive these projects if PMC
 decides to start maintaining them again.
>>> 
>>> 
> 

Re: [D] java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId` options [logging-log4j2]

[via GitHub]

GitHub user THausherr 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

```
org.apache.maven.plugins
maven-compiler-plugin


generate-log4j-plugin-descriptor

compile

process-classes

only


org.apache.logging.log4j
log4j-core
${log4j2.version}




org.apache.logging.log4j.core.config.plugins.processor.PluginProcessor

org.apache.logging.log4j.core.config.plugins.processor.GraalVmProcessor



-Alog4j.graalvm.groupId=${project.groupId}

-Alog4j.graalvm.artifactId=${project.artifactId}





```

and I do have a plugin 

```
@Plugin(name = "DebugLogAppender", category = "Core", elementType = "appender", 
printObject = true)
public class DebugLogAppender extends AbstractAppender

```

The subproject is here (the above segment has been removed because I reverted 
the change):
https://github.com/apache/pdfbox/tree/trunk/debugger

GitHub link: 
https://github.com/apache/logging-log4j2/discussions/3755#discussioncomment-13511992


This is an automatically sent email for dev@logging.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@logging.apache.org

Re: [D] java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId` options [logging-log4j2]

[via GitHub]

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

Hi @ratoaq2,

Thanks for the detailed error log — it's very helpful.

>From what you've shared, the issue is occurring during the `default-compile` 
>Maven Compiler Plugin execution, not in the custom 
>`generate-log4j-plugin-descriptor` execution you configured. Specifically:

```
[INFO] --- compiler:3.14.0:compile (default-compile) @ common ---
[INFO] Compiling with eclipse [...] to target/classes
[ERROR] Internal compiler error: java.lang.IllegalArgumentException: 
The `GraalVmProcessor` annotation processor is missing the required 
`log4j.graalvm.groupId` and `log4j.graalvm.artifactId` options.
```

If you want to use a separate execution for annotation processing, you need to 
disable annotation processing in `default-compile`:

```xml

  default-compile
  
none
  

```

If, on the other hand, you want to perform both compilation and annotation 
processing (Log4j plugin descriptor + GraalVM metadata) **in a single Maven 
execution**, you can fully configure the `default-compile` phase like this:

```xml

  org.apache.maven.plugins
  maven-compiler-plugin
  3.14.0
  

  org.codehaus.plexus
  plexus-compiler-eclipse
  2.15.0

  
  

eclipse
21

none
  
  

  default-compile
  

only

  
org.apache.logging.log4j
log4j-core
2.25.0
  


  

org.apache.logging.log4j.core.config.plugins.processor.PluginProcessor
  
  

org.apache.logging.log4j.core.config.plugins.processor.GraalVmProcessor
  


  
  -Alog4j.graalvm.groupId=${project.groupId}
  -Alog4j.graalvm.artifactId=${project.artifactId}

  

  

```


GitHub link: 
https://github.com/apache/logging-log4j2/discussions/3755#discussioncomment-13512223


This is an automatically sent email for dev@logging.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@logging.apache.org

Re: [D] java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId` options [logging-log4j2]

[via GitHub]

GitHub user ppkarwasz edited a comment on the discussion: 
java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor 
is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId` 
options

Hi @ratoaq2,

Thanks for the detailed error log — it's very helpful.

>From what you've shared, the issue is occurring during the `default-compile` 
>Maven Compiler Plugin execution, not in the custom 
>`generate-log4j-plugin-descriptor` execution you configured. Specifically:

```
[INFO] --- compiler:3.14.0:compile (default-compile) @ common ---
[INFO] Compiling with eclipse [...] to target/classes
[ERROR] Internal compiler error: java.lang.IllegalArgumentException: 
The `GraalVmProcessor` annotation processor is missing the required 
`log4j.graalvm.groupId` and `log4j.graalvm.artifactId` options.
```

If you want to use a separate execution for annotation processing, you need to 
disable annotation processing in `default-compile`:

```xml

  default-compile
  
none
  

```

If, on the other hand, you want to perform both compilation and annotation 
processing (Log4j plugin descriptor + GraalVM metadata) **in a single Maven 
execution**, you can fully configure the `default-compile` phase like this:

```xml

  org.apache.maven.plugins
  maven-compiler-plugin
  3.14.0
  

  org.codehaus.plexus
  plexus-compiler-eclipse
  2.15.0

  
  

eclipse
21

none
  
  

  default-compile
  

only

  
org.apache.logging.log4j
log4j-core
2.25.0
  


  

org.apache.logging.log4j.core.config.plugins.processor.PluginProcessor
  
  

org.apache.logging.log4j.core.config.plugins.processor.GraalVmProcessor
  


  
  -Alog4j.graalvm.groupId=${project.groupId}
  -Alog4j.graalvm.artifactId=${project.artifactId}

  

  

```

I hope that helps solving your problem.


GitHub link: 
https://github.com/apache/logging-log4j2/discussions/3755#discussioncomment-13512223


This is an automatically sent email for dev@logging.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@logging.apache.org

Re: [D] java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId` options [logging-log4j2]

[via GitHub]

GitHub user THausherr 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

I tried the last change with default-compile and now the project that follows 
the problematic project claims that the previous package doesn't exist. I 
looked into the repository directory, the jar files are there, but much 
smaller. It turned out the class files are missing.

GitHub link: 
https://github.com/apache/logging-log4j2/discussions/3755#discussioncomment-13512509


This is an automatically sent email for dev@logging.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@logging.apache.org

Re: [D] java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId` options [logging-log4j2]

[via GitHub]

GitHub user THausherr 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

Thank you! I also suggest that the log4j documentation be updated, with the 
links that you provided in your PR.

GitHub link: 
https://github.com/apache/logging-log4j2/discussions/3755#discussioncomment-13516189


This is an automatically sent email for dev@logging.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@logging.apache.org