AnttiMK opened a new issue, #3753:
URL: https://github.com/apache/logging-log4j2/issues/3753
## Description
All Javadocs for log4j listed on
https://logging.apache.org/log4j/2.x/javadoc.html are unavailable, and just
return a "Page not found".
:
```xml
ppkarwasz commented on PR #3372:
URL: https://github.com/apache/logging-log4j2/pull/3372#issuecomment-2979985822
Hi @norrisjeremy,
Thanks for your thoughtful and detailed questions—these are all excellent
points, and I really appreciate you taking the time to raise them.
> 1. S
hankem opened a new issue, #3754:
URL: https://github.com/apache/logging-log4j2/issues/3754
## Description
log4j 2.25.0's dependency `com.github.spotbugs:spotbugs-annotations:4.9.3`
is only compatible with JVM runtime version 11+
## Configuration
**Version:** 2.25.0
vy commented on PR #3545:
URL: https://github.com/apache/logging-log4j2/pull/3545#issuecomment-2981733490
@timtebeek, that is indeed a regression. Log4j 2 targets Java 8 and there
are no plans to change that. You should be able to workaround the issue by
excluding that dependency – `spotbug
timtebeek commented on PR #3545:
URL: https://github.com/apache/logging-log4j2/pull/3545#issuecomment-2981743912
Ah thanks for the quick confirm! I'd intentionally posted here as I didn't
want to overwhelm with a new PR/issue in case it was intentional. Thanks for
the quick response and upt
vy commented on PR #3545:
URL: https://github.com/apache/logging-log4j2/pull/3545#issuecomment-2981740936
@timtebeek, no need for a new issue. As I type to you, somebody already
submitted an issue for that: #3754.
--
This is an automated message from the Apache Git Service.
To respond to
hankem commented on issue #3754:
URL:
https://github.com/apache/logging-log4j2/issues/3754#issuecomment-2981740257
Downgrading to SpotBugs <
[4.9.0](https://github.com/spotbugs/spotbugs/releases/tag/4.9.0) solves the
issue:
```diff
--- a/log4j-parent/pom.xml
+++ b/log4j-parent/pom
vy commented on issue #3754:
URL:
https://github.com/apache/logging-log4j2/issues/3754#issuecomment-2981747504
@hankem, thanks so much for the report. We need to downgrade the dependency,
pin it for dependabot, and see if we can come up with a check to avoid having
the same problem again.
vy commented on issue #3066:
URL:
https://github.com/apache/logging-log4j2/issues/3066#issuecomment-2981762341
@dsvensson, we do not posses much Gradle experience, would you mind
elaborating on the problem, please? I don't see anything suspicious in [the
Log4j BOM recently published with v
github-actions[bot] merged PR #45:
URL: https://github.com/apache/logging-log4j-jmx-gui/pull/45
--
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: notifica
timtebeek commented on PR #3545:
URL: https://github.com/apache/logging-log4j2/pull/3545#issuecomment-2981702365
@ppkarwasz following [yesterday's v2.25.0
release](https://github.com/apache/logging-log4j2/releases/tag/rel%2F2.25.0)
I'm seeing the following issue when targeting Java 8:
``
ppkarwasz opened a new issue, #3750:
URL: https://github.com/apache/logging-log4j2/issues/3750
In the `main` branch, all withers (builder method following the `with`
pattern) have been replaced with setter methods for consistency and clarity.
To ensure a smooth upgrade path and better
github-actions[bot] merged PR #77:
URL: https://github.com/apache/logging-log4j-audit-sample/pull/77
--
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: not
dependabot[bot] opened a new pull request, #77:
URL: https://github.com/apache/logging-log4j-audit-sample/pull/77
Bumps
[org.apache.logging.log4j:log4j-bom](https://github.com/apache/logging-log4j2)
from 2.24.3 to 2.25.0.
Release notes
Sourced from https://github.com/apache/loggin
norrisjeremy commented on PR #3372:
URL: https://github.com/apache/logging-log4j2/pull/3372#issuecomment-2980153817
Hi @ppkarwasz,
Thank you for your detailed response.
To answer your question about the impact: we deliberately run compiler
warnings & deprecations set to errors
18 matches
Mail list logo