Skip to content

fix: Make GraalVmProcessor Arguments Optional #3772

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: 2.x
Choose a base branch
from

Conversation

ppkarwasz
Copy link
Contributor

Fixes #3771

This PR makes the -Alog4j.graalvm.groupId and -Alog4j.graalvm.artifactId arguments optional.

  • If no arguments are provided, metadata is stored in:

    META-INF/native-image/log4j-generated
    

    Previously an error was thrown.

  • If arguments are provided, files go to:

    META-INF/native-image/log4j-generated/<groupId>/<artifactId>
    

    Previously META-INF/native-image/<groupId>/<artifactId> was used. The new path prevents collisions with user-provided metadata.

Fixes #3771

This PR makes the `-Alog4j.graalvm.groupId` and `-Alog4j.graalvm.artifactId` arguments optional.

* If **no arguments** are provided, metadata is stored in:

  ```
  META-INF/native-image/log4j-generated
  ```
  Previously an error was thrown.

* If **arguments are provided**, files go to:

  ```
  META-INF/native-image/log4j-generated/<groupId>/<artifactId>
  ```
  Previously `META-INF/native-image/<groupId>/<artifactId>` was used. The new path prevents collisions with user-provided metadata.
@ppkarwasz ppkarwasz moved this from To triage to In review in Log4j bug tracker Jun 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: In review
Development

Successfully merging this pull request may close these issues.

Make GraalVmProcessor Arguments Optional
1 participant