github-actions[bot] commented on PR #3259:
URL: https://github.com/apache/logging-log4j2/pull/3259#issuecomment-2509609137
Job
Requested goals
Build Tool Version
Build Outcome
Build Scan®
build-
swebb2066 opened a new pull request, #438:
URL: https://github.com/apache/logging-log4cxx/pull/438
Remove references to the already released version
--
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 t
swebb2066 merged PR #437:
URL: https://github.com/apache/logging-log4cxx/pull/437
--
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: notifications-unsubscr
eldwrjwt commented on issue #3257:
URL:
https://github.com/apache/logging-log4j2/issues/3257#issuecomment-2509081129
PR Submitted in #3259 for FailoverAppender
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL a
ppkarwasz opened a new pull request, #3258:
URL: https://github.com/apache/logging-log4j2/pull/3258
This adds a `log4j.plugin.enableBndAnnotations` option to the
`PluginProcessor`. Its default value is inferred from the compiler classpath.
We also rename the `pluginPackage` option to
PavelTurk commented on issue #3255:
URL:
https://github.com/apache/logging-log4j2/issues/3255#issuecomment-2508901655
@ppkarwasz
The problem is not decompilation (NB also has a Java decompiler plugin); the
problem lies in deviating from the standard. But these are just thoughts out
ppkarwasz commented on issue #3255:
URL:
https://github.com/apache/logging-log4j2/issues/3255#issuecomment-2508894862
> I am afraid it is not a good solution. Because it is a standard way to get
sources from `-sources.jar` files. For example, when I work in IDE (NB) I do
right click on dep
PavelTurk commented on issue #3255:
URL:
https://github.com/apache/logging-log4j2/issues/3255#issuecomment-2508880014
@ppkarwasz
> I don't believe this is a big problem, since the information in
`module-info.class` can be extracted quite easily by any decompiler or `jar -d`.
I am
