Siedlerchr commented on PR #3759:
URL: https://github.com/apache/logging-log4j2/pull/3759#issuecomment-2985730503
@ppkarwasz Thanks for the detailed explanation. It's probably easier if you
take over this PR/fix
--
This is an automated message from the Apache Git Service.
To respond to
ppkarwasz commented on PR #3759:
URL: https://github.com/apache/logging-log4j2/pull/3759#issuecomment-2985504984
> I don't know but it was clearly missing in the parent pom, so maybe that
got resolved instead?
To expand a bit on what @vy pointed out:
* The `jspecify.version` pr
Siedlerchr commented on PR #3759:
URL: https://github.com/apache/logging-log4j2/pull/3759#issuecomment-2985382835
I don't know but it was clear missing in the parent pom, so maybe that got
resolved instead?
--
This is an automated message from the Apache Git Service.
To respond to the me
jeanbza commented on issue #2447:
URL:
https://github.com/apache/logging-log4j2/issues/2447#issuecomment-2985370633
Howdy. We ran into this, or something very similar to this, today. We're
using `ConsoleAppender`.
Our disk was 100% full at the time, which I think is related? Here's p
vy commented on PR #3759:
URL: https://github.com/apache/logging-log4j2/pull/3759#issuecomment-2985363033
The actual fix might be more convoluted. `jspecify.version` already exist in
`/pom.xml`, though gets removed during BOM-ification right before deployment.
--
This is an automated mess
Siedlerchr opened a new pull request, #3759:
URL: https://github.com/apache/logging-log4j2/pull/3759
Add missing jspeficy version defintion
Fixes https://github.com/apache/logging-log4j2/issues/3758
> [!IMPORTANT]
> Base your changes on `2.x` branch if you are targeting Log
Siedlerchr opened a new issue, #3758:
URL: https://github.com/apache/logging-log4j2/issues/3758
## Description
We noticed that the jspecify version entry is missing, causing publishing
problems with jbang. There is no definition for the version at the top.
```
org.js
ppkarwasz closed issue #3753: Javadocs return "Page not found" on website
URL: https://github.com/apache/logging-log4j2/issues/3753
--
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 commen
ppkarwasz commented on issue #3753:
URL:
https://github.com/apache/logging-log4j2/issues/3753#issuecomment-2984839784
@AnttiMK,
Thank you for the report! It should be fixed now.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to
ppkarwasz opened a new pull request, #3757:
URL: https://github.com/apache/logging-log4j2/pull/3757
The Javadoc site generation broke after upgrading to Maven Javadoc Plugin
3.10.0 due to a change in the output directory structure (see
apache/maven-javadoc-plugin#1163). This update adjusts
jhl221123 opened a new pull request, #3756:
URL: https://github.com/apache/logging-log4j2/pull/3756
This pull request addresses issue #3750 by deprecating all withers in
builder classes and introducing setters as replacements. All internal usages
and related tests have been updated to use t
ppkarwasz commented on PR #3372:
URL: https://github.com/apache/logging-log4j2/pull/3372#issuecomment-2984789617
Hi @norrisjeremy,
> To answer your question about the impact: we deliberately run compiler
warnings & deprecations set to errors for our internal apps, so that they
immedi
FreeAndNil opened a new pull request, #258:
URL: https://github.com/apache/logging-log4net/pull/258
- Asynchronous Sending for RemoteSyslogAppender in log4net #255
- added unit test
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to
dsvensson commented on issue #3066:
URL:
https://github.com/apache/logging-log4j2/issues/3066#issuecomment-2983180963
oooh... found a cli tool hiding in my tree that actually used log4j api
while the rest used slf4j. Thank you for your detailed answer.
--
This is an automated message fro
14 matches
Mail list logo
