dependabot[bot] opened a new pull request, #1:
URL: https://github.com/apache/logging-log4j-jmx-gui/pull/1
Bumps
[com.github.spotbugs:spotbugs-annotations](https://github.com/spotbugs/spotbugs)
from 4.7.3 to 4.8.0.
Release notes
Sourced from https://github.com/spotbugs/spotbugs/re
vy merged PR #1:
URL: https://github.com/apache/logging-log4j-jmx-gui/pull/1
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@logging.apa
MoonLord-LM commented on issue #2:
URL:
https://github.com/apache/logging-log4j-jmx-gui/issues/2#issuecomment-1785860608
https://github.com/apache/logging-log4j-jmx-gui/assets/8104133/4729d0f3-5a70-4dae-9751-3444d33752a0";>
--
This is an automated message from the Apache Git Service.
MoonLord-LM commented on issue #2:
URL:
https://github.com/apache/logging-log4j-jmx-gui/issues/2#issuecomment-1785862128
https://mvnrepository.com/artifact/org.apache.logging.log4j/log4j-bom/2.21.1
--
This is an automated message from the Apache Git Service.
To respond to the message, ple
ppkarwasz commented on issue #2:
URL:
https://github.com/apache/logging-log4j-jmx-gui/issues/2#issuecomment-1785870820
@MoonLord-LM,
Thank you for the report. The problem is that `log4j-bom` contains a bad
entry, so I am closing this issue and keeping apache/logging-log4j2#1926
--
ppkarwasz closed issue #2: This package is not in the mvn repo?
URL: https://github.com/apache/logging-log4j-jmx-gui/issues/2
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To
dependabot[bot] opened a new pull request, #1:
URL: https://github.com/apache/logging-log4j-jakarta/pull/1
Bumps [org.junit:junit-bom](https://github.com/junit-team/junit5) from
5.10.0 to 5.10.1.
Release notes
Sourced from https://github.com/junit-team/junit5/releases";>org.junit:j
dependabot[bot] opened a new pull request, #2:
URL: https://github.com/apache/logging-log4j-jakarta/pull/2
Bumps jakarta.platform:jakarta.jakartaee-bom from 9.1.0 to 10.0.0.
[ from
5.5.0 to 5.7.0.
Release notes
Sourced from https://github.com/mockito/mockito/releases";>org.mockito:m
github-actions[bot] commented on PR #4:
URL:
https://github.com/apache/logging-log4j-jakarta/pull/4#issuecomment-1816983082
Changes are applied by CI in 4ca37fae4e0594bd9dc5ed4e5c069f69faf23df2
--
This is an automated message from the Apache Git Service.
To respond to the message, please
github-actions[bot] closed pull request #4: Bump
org.springframework:spring-framework-bom from 6.0.13 to 6.1.0
URL: https://github.com/apache/logging-log4j-jakarta/pull/4
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use th
github-actions[bot] commented on PR #3:
URL:
https://github.com/apache/logging-log4j-jakarta/pull/3#issuecomment-1816996007
Changes are applied by CI in f6bbf6258ee43d60118cd0a4e1a9fda99a560e28
--
This is an automated message from the Apache Git Service.
To respond to the message, please
github-actions[bot] closed pull request #3: Bump org.mockito:mockito-bom from
5.5.0 to 5.7.0
URL: https://github.com/apache/logging-log4j-jakarta/pull/3
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go
ppkarwasz commented on PR #1:
URL:
https://github.com/apache/logging-log4j-jakarta/pull/1#issuecomment-1817028310
@dependabot recreate
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specifi
github-actions[bot] closed pull request #1: Bump org.junit:junit-bom from
5.10.0 to 5.10.1
URL: https://github.com/apache/logging-log4j-jakarta/pull/1
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to
github-actions[bot] commented on PR #1:
URL:
https://github.com/apache/logging-log4j-jakarta/pull/1#issuecomment-1817035848
Changes are applied by CI in 6fb89eb4d389963b6e5f95fca1ae0cff5bbab592
--
This is an automated message from the Apache Git Service.
To respond to the message, please
ppkarwasz commented on PR #5:
URL:
https://github.com/apache/logging-log4j-jakarta/pull/5#issuecomment-1824930468
@dependabot rebase
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific
github-actions[bot] commented on PR #5:
URL:
https://github.com/apache/logging-log4j-jakarta/pull/5#issuecomment-1824937518
Changes are applied by CI in 14a91d49c6fe432e9df0e0b8429d01dbf036bf13
--
This is an automated message from the Apache Git Service.
To respond to the message, please
github-actions[bot] closed pull request #5: Bump
org.springframework:spring-framework-bom from 6.1.0 to 6.1.1
URL: https://github.com/apache/logging-log4j-jakarta/pull/5
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
dependabot[bot] opened a new pull request, #3:
URL: https://github.com/apache/logging-log4j-jmx-gui/pull/3
Bumps org.apache.logging.log4j:log4j-core from 2.21.1 to 2.22.0.
[.
You need to programmatically do it.
GitHub link:
https://g
GitHub user vy edited a comment on the discussion: How do I register a
StatusListener in configuration?
This is explained in [the Status Logger
documentation](https://logging.apache.org/log4j/2.x/manual/status-logger.html#listeners).
You need to programmatically do it. This is also stated in
GitHub user ppkarwasz added a comment to the discussion: Provide a Layout to
StatusLogger
> The error messages are somewhat useful to me as a user, but stack traces from
> inside of log4j are only useful for maintainers of the log4j library.
There are [options for the date format of status
l
GitHub user voddan added a comment to the discussion: Provide a Layout to
StatusLogger
I see. That kinda makes sense, however I wish there was a way to at least turn
of the stack traces. The error messages are somewhat useful to me as a user,
but stack traces from inside of log4j are only use
GitHub user ppkarwasz added a comment to the discussion: Is using %uuid{RANDOM}
pattern in JsonTemplateLayout considered garbage-free?
> However, it definitely makes more sense to ensure the UUID is injected into
> the LogEvent before any Appenders process it.
This is the main problem: `%uuid
GitHub user rgoers added a comment to the discussion: Is using %uuid{RANDOM}
pattern in JsonTemplateLayout considered garbage-free?
I would need to read more on the subject but I have to assume this is very
similar to the problem I faced with Flume. It guarantees delivery but it
doesn't guara
GitHub user rgoers added a comment to the discussion: Is using %uuid{RANDOM}
pattern in JsonTemplateLayout considered garbage-free?
I hate to disagree Piotr, but our time based uuid exists for exactly this use
case. It will provide a unique value across all servers. While it isn’t going
to be
GitHub user ppkarwasz added a comment to the discussion: Is using %uuid{RANDOM}
pattern in JsonTemplateLayout considered garbage-free?
Neither one is GC-free. Each one will create an instance of
[`UUID`](https://docs.oracle.com/javase/8/docs/api/java/util/UUID.html) and
`String`. Scalar repla
GitHub user ppkarwasz added a comment to the discussion: Is using %uuid{RANDOM}
pattern in JsonTemplateLayout considered garbage-free?
**BTW**: Using `%uuid` as value for
[logging.googleapis.com/insertId](https://cloud.google.com/logging/docs/reference/v2/rest/v2/LogEntry#FIELDS.insert_id)
do
GitHub user Class-New added a comment to the discussion:
TimeBasedTriggeringPolicy and CronTriggeringPolicy
Because the project wants to roll the daily logs under the corresponding date
directory, for example, the logs that occurred on 2025-04-02 are rolled under
the folder 2025-04-02. But wh
GitHub user ppkarwasz added a comment to the discussion:
TimeBasedTriggeringPolicy and CronTriggeringPolicy
@Class-New,
As [documented on our
website](https://logging.apache.org/log4j/2.x/manual/appenders/rolling-file.html#Policies):
> The effects of using **both** time-based triggering poli
GitHub user ppkarwasz added a comment to the discussion: Is using %uuid{RANDOM}
pattern in JsonTemplateLayout considered garbage-free?
I am not saying that `%uuid` will give the **same** value for **different** log
events, but that it will give **different** value for the **same** log event if
GitHub user vy added a comment to the discussion: Custom rewrite appender not
working when used like dependency on spring boot app
Project A has a dependency on Project B, which contains a custom appender, that
you want to use in the `log4j2.xml` of Project A, right?
1. How do you package Pro
GitHub user vy added a comment to the discussion: Need help on migrating from
PluginManager to PluginProcessor
@VenkataSubbareddy-GY, when you compile your code using the annotation
processor, do you see a `Log4j2Plugins.dat` gets auto-generated? Does it
contain your custom plugins?
GitHub l
GitHub user Class-New added a comment to the discussion:
TimeBasedTriggeringPolicy and CronTriggeringPolicy
Thank you for your answer
GitHub link:
https://github.com/apache/logging-log4j2/discussions/3587#discussioncomment-12861070
This is an automatically sent email for dev@logging.apa
GitHub user voddan added a comment to the discussion: How do I register a
StatusListener in configuration?
@vy How would it look in a project? If you can share an example project where
you do it like that, it would be great.
Simply put, I don't understand where I should put this line of code
GitHub user vy added a comment to the discussion: Provide a Layout to
StatusLogger
No, it is not possible and, IMHO, this is a good thing. Status Logger is the
logger for the logger – that is, we need to keep its feature set at minimum.
Consider it like a `printf()` on steroids.
> When I get
GitHub user vy added a comment to the discussion: How do I register a
StatusListener in configuration?
```
StatusLogger.getLogger().registerListener(...)
```
You need to place this snippet as early as possible in your application
initialization, e.g.,
```
static {
StatusLogger.getLogger(
GitHub user ViliusS edited a comment on the discussion: Is using %uuid{RANDOM}
pattern in JsonTemplateLayout considered garbage-free?
> **BTW**: Using `%uuid` as value for
> [logging.googleapis.com/insertId](https://cloud.google.com/logging/docs/reference/v2/rest/v2/LogEntry#FIELDS.insert_id)
GitHub user ViliusS edited a comment on the discussion: Is using %uuid{RANDOM}
pattern in JsonTemplateLayout considered garbage-free?
> **BTW**: Using `%uuid` as value for
> [logging.googleapis.com/insertId](https://cloud.google.com/logging/docs/reference/v2/rest/v2/LogEntry#FIELDS.insert_id)
GitHub user ppkarwasz added a comment to the discussion: Is using %uuid{RANDOM}
pattern in JsonTemplateLayout considered garbage-free?
> Alternatively, `insertId` could be omitted completely, so GCP would generate
> their own IDs.
This is probably the route I would choose. The only purpose of
GitHub user ViliusS edited a comment on the discussion: Is using %uuid{RANDOM}
pattern in JsonTemplateLayout considered garbage-free?
> **BTW**: Using `%uuid` as value for
> [logging.googleapis.com/insertId](https://cloud.google.com/logging/docs/reference/v2/rest/v2/LogEntry#FIELDS.insert_id)
GitHub user ViliusS added a comment to the discussion: Is using %uuid{RANDOM}
pattern in JsonTemplateLayout considered garbage-free?
> **BTW**: Using `%uuid` as value for
> [logging.googleapis.com/insertId](https://cloud.google.com/logging/docs/reference/v2/rest/v2/LogEntry#FIELDS.insert_id)
>
GitHub user ElaHuskovic68 edited a discussion: log4j-1.2.13.jar substitution in
v.2.17.1
Inside war file at path /WEB-INF/lib we found log4j-1.2.13 which needs to be
replaced with log4j-2.17.1.jar. In
apache-log4j-2.17.1-bin there is no that file. What jar file replaces old one?
Thanks!
Gi
GitHub user ElaHuskovic68 added a comment to the discussion: log4j-1.2.13.jar
substitution in v.2.17.1
Not in our case. We though just to replace .jar file but no proper match in
higher version.
GitHub link:
https://github.com/apache/logging-log4j2/discussions/3656#discussioncomment-1309170
GitHub user vy added a comment to the discussion: log4j-1.2.13.jar substitution
in v.2.17.1
@ElaHuskovic68, does the [Migrating from Log4j
1](https://logging.apache.org/log4j/2.x/migrate-from-log4j1.html) page help?
GitHub link:
https://github.com/apache/logging-log4j2/discussions/3656#discu
GitHub user ppkarwasz added a comment to the discussion: log4j-1.2.13.jar
substitution in v.2.17.1
Can you provide us with some feedback on the migration page? Where does it come
short of your expectations?
To better understand, how we can help, can you tell us:
- Do you have access to the s
GitHub user FreeAndNil added a comment to the discussion: Question about
asynchronous writing by log4net
@yktnoriri I've converted you issue into a discussion.
I was able to reproduce your problem once, but only once.
Can you set a breakpoint in
https://github.com/apache/logging-log4net/blob
GitHub user ElaHuskovic68 added a comment to the discussion: log4j-1.2.13.jar
substitution in v.2.17.1
hi @ppkarwasz - thank you for your answer.
This is third party application, I dont have source code, only war file which
contains 1.x version of log4j jar file. I checked with Owner and it lo
GitHub user perry2of5 added a comment to the discussion: log4j-1.2.13.jar
substitution in v.2.17.1
Some people have been known to recommend Reload4j 1.2.18 as a replacement for
log4j 1.2.17
GitHub link:
https://github.com/apache/logging-log4j2/discussions/3656#discussioncomment-13135934
---
GitHub user lalo-mx added a comment to the discussion: log4j-1.2.13.jar
substitution in v.2.17.1
> Some people have been known to recommend Reload4j 1.2.18 as a replacement for
> log4j 1.2.17
https://reload4j.qos.ch/
> Initiated by Ceki Gülcü, the original author of Apache log4j 1.x, the
>
GitHub user ppkarwasz edited a comment on the discussion: log4j-1.2.13.jar
substitution in v.2.17.1
@ElaHuskovic68,
> This is third party application, I dont have source code, only war file which
> contains 1.x version of log4j jar file.
Thanks for clarifying your situation — dealing with th
GitHub user ppkarwasz added a comment to the discussion: log4j-1.2.13.jar
substitution in v.2.17.1
@ElaHuskovic68,
> This is third party application, I dont have source code, only war file which
> contains 1.x version of log4j jar file.
Thanks for clarifying your situation — dealing with thi
GitHub user ppkarwasz added a comment to the discussion: log4j-1.2.13.jar
substitution in v.2.17.1
Reload4j is a **valid temporary** replacement for Log4j 1, and I can certainly
recommend it for that purpose. While it introduces some breaking changes
compared to Log4j `1.2.17`, it is **99% bi
GitHub user mmahant17 added a comment to the discussion: log4j version 2.17.1
Thank you for your prompt response.
GitHub link:
https://github.com/apache/logging-log4j2/discussions/3679#discussioncomment-13212196
This is an automatically sent email for dev@logging.apache.org.
To unsubscri
GitHub user ppkarwasz added a comment to the discussion: log4j version 2.17.1
> Could you please confirm if Log4j version 2.17.1 is supported?
Whether we "support" Log4j version `2.17.0` depends on how you define
"support," so let’s break it down:
- We **no longer** maintain the `2.17.x` mino
GitHub user ppkarwasz edited a comment on the discussion: log4j version 2.17.1
> Could you please confirm if Log4j version 2.17.1 is supported?
Whether we "support" Log4j version `2.17.0` depends on how you define
"support," so let’s break it down:
- We **no longer** maintain the `2.17.x` min
GitHub user ppkarwasz added a comment to the discussion: log4j version 2.17.1
That’s an excellent answer — thank you!
Just to add for completeness: version 2.17.0 was never affected by
CVE-2021-44832. This was confirmed in a later review (see
apache/logging-site#6).
GitHub link:
https://gith
GitHub user perry2of5 added a comment to the discussion: log4j version 2.17.1
Please refer to the security page:
https://logging.apache.org/security.html
Also, mvnrepository.com provides links to most security vulnerabilities from
affected artifacts. For example, on log4j-core, it doesn't show
GitHub user ppkarwasz added a comment to the discussion: Timeline for
org.apache.logging.log4j:log4j-api:3.0.0 release?
You can follow the progress of release `2.25.0` in [its dedicated mailing list
thread](https://lists.apache.org/thread/9gshmgk75llkzvmns6ocks1b5h7n90qp).
GitHub link:
htt
GitHub user jluehe edited a comment on the discussion: Timeline for
org.apache.logging.log4j:log4j-api:3.0.0 release?
Created Issue https://github.com/apache/logging-log4j2/issues/3686
GitHub link:
https://github.com/apache/logging-log4j2/discussions/3682#discussioncomment-13255364
This
GitHub user jluehe edited a comment on the discussion: Timeline for
org.apache.logging.log4j:log4j-api:3.0.0 release?
@ppkarwasz, for your review: https://github.com/apache/logging-log4j2/pull/3689
GitHub link:
https://github.com/apache/logging-log4j2/discussions/3682#discussioncomment-132554
GitHub user yktnoriri closed a discussion: Question about asynchronous writing
by log4net
Hello there,
We are currently using log4net for logging in our .NET Framework 4.8
application, developed with Microsoft Visual Studio Professional 2022 Version
17.12.3.
We have observed a potential iss
GitHub user FreeAndNil closed the discussion with a comment: Question about
asynchronous writing by log4net
Please reopen when you find the time to respond.
GitHub link:
https://github.com/apache/logging-log4net/discussions/243#discussioncomment-13275414
This is an automatically sent em
GitHub user jluehe edited a comment on the discussion: Timeline for
org.apache.logging.log4j:log4j-api:3.0.0 release?
@ppkarwasz, for your review: https://github.com/apache/logging-log4j2/pull/3690
GitHub link:
https://github.com/apache/logging-log4j2/discussions/3682#discussioncomment-132554
GitHub user jluehe added a comment to the discussion: Timeline for
org.apache.logging.log4j:log4j-api:3.0.0 release?
@ppkarwasz, can you tell me what is the ETA for the `2.25.0` release? Thanks!
GitHub link:
https://github.com/apache/logging-log4j2/discussions/3682#discussioncomment-13262982
GitHub user jluehe edited a comment on the discussion: Timeline for
org.apache.logging.log4j:log4j-api:3.0.0 release?
@ppkarwasz, can you tell me what is the ETA for the `2.25.0` release? Even an
approximate date would help! Thanks!
GitHub link:
https://github.com/apache/logging-log4j2/discu
GitHub user ppkarwasz added a comment to the discussion: Parameterized Info
intermittently throws IllegalArgumentException
@arbardhan,
Did you test with the latest release (`2.24.3`)?
GitHub link:
https://github.com/apache/logging-log4j2/discussions/3695#discussioncomment-13288046
This
GitHub user ppkarwasz added a comment to the discussion: Parameterized Info
intermittently throws IllegalArgumentException
> But can you think of scenarios where this may occur ?
In version `2.21.0`, the parameter formatting logic was changed to **strictly
enforce** a match between `{}` place
GitHub user arbardhan edited a discussion: Parameterized Info intermittently
throws IllegalArgumentException
I log 8 parameters using {} in log.info this comes from a httpServlet request
preHandlePath. This log statement sometimes throwa IAE exception stating only 5
arguments provided for 8 p
GitHub user arbardhan added a comment to the discussion: Parameterized Info
intermittently throws IllegalArgumentException
2.24.3 is not available under our org enterprise distribution yet - pending
approval. We only go back to older versions. But can you think of scenarios
where this may occ
GitHub user ppkarwasz added a comment to the discussion: Timeline for
org.apache.logging.log4j:log4j-api:3.0.0 release?
Thank you for the clarification. As far as I’m aware, the Log4j API itself
doesn’t directly depend on Java EE 8 or Jakarta EE 9 APIs. Could you point to
the specific usage o
GitHub user ppkarwasz added a comment to the discussion: Timeline for
org.apache.logging.log4j:log4j-api:3.0.0 release?
There will be **no `3.0.0` release of the [Log4j
API](https://logging.apache.org/log4j/2.x/manual/api.html)**. This is
intentional: both Log4j Core 2 and Log4j Core 3 are de
GitHub user garydgregory added a comment to the discussion: Timeline for
org.apache.logging.log4j:log4j-api:3.0.0 release?
And welcome to the pain and confusing we are forcing on our users with this
confusing version policy 😞
GitHub link:
https://github.com/apache/logging-log4j2/discussions
GitHub user jluehe added a comment to the discussion: Timeline for
org.apache.logging.log4j:log4j-api:3.0.0 release?
@ppkarwasz, we are looking for a Jakarta EE9 compatible version of
`org.apache.logging.log4j:log4j-api`. We found that version `2.24.3` is not
Jakarta EE9 compatible (as it con
GitHub user jluehe added a comment to the discussion: Timeline for
org.apache.logging.log4j:log4j-api:3.0.0 release?
Thanks for your response, @ppkarwasz!
Yes, the `javax` reference in `Constants.java` is "benign".
The problematic reference is here:
https://github.com/apache/logging-log4j2
GitHub user ppkarwasz added a comment to the discussion: Timeline for
org.apache.logging.log4j:log4j-api:3.0.0 release?
Great catch! :100:
That’s some legacy code we originally included to support Java 7. Since version
`2.13.0`, our baseline has been Java 8, so we can now safely use
`java.ut
GitHub user jluehe added a comment to the discussion: Timeline for
org.apache.logging.log4j:log4j-api:3.0.0 release?
Created https://github.com/apache/logging-log4j2/issues/3686
GitHub link:
https://github.com/apache/logging-log4j2/discussions/3682#discussioncomment-13255364
This is an
GitHub user jluehe added a comment to the discussion: Timeline for
org.apache.logging.log4j:log4j-api:3.0.0 release?
Yes, @ppkarwasz, I'd be more than happy to contribute a PR against the `2.x`
branch, in time for the `2.25.0` release! Please stay tuned!
GitHub link:
https://github.com/apach
GitHub user jluehe added a comment to the discussion: Timeline for
org.apache.logging.log4j:log4j-api:3.0.0 release?
@ppkarwasz, for your review: https://github.com/apache/logging-log4j2/pull/3687
GitHub link:
https://github.com/apache/logging-log4j2/discussions/3682#discussioncomment-1325540
GitHub user ppkarwasz added a comment to the discussion: Attribute 'additivity'
is not allowed to appear in element 'Logger'
Hi @jorge683,
Yes, this is indeed a bug — tracked here: apache/logging-log4j-tools#135 — in
the [Log4j Docgen
tool](https://logging.apache.org/log4j/tools/log4j-docgen
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.plex
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
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.plex
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
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 t
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 agree. I have no annotation processors configured in my pom, all ru
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 disabl
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 submit
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
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 proces
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 Gra
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
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 `GraalVmProcess
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 tha
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.
1 - 100 of 182 matches
Mail list logo
