ppkarwasz opened a new pull request, #401:
URL: https://github.com/apache/logging-parent/pull/401
Due to the replacement of Maven Deploy Plugin with Nexus Staging Plugin, the
staging process of the binary distribution archive fails.
Since the Nexus Staging Plugin also creates a local
ppkarwasz opened a new issue, #400:
URL: https://github.com/apache/logging-parent/issues/400
Commit 769fd981041b1b9244c146ceb301cba076496005 modified the "Staging
distribution artifacts" to use `deploy:deploy` directly, instead of using a
Maven lifecycle goal. This causes release builds to
ppkarwasz merged PR #3707:
URL: https://github.com/apache/logging-log4j2/pull/3707
--
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-unsubsc
vy merged PR #3677:
URL: https://github.com/apache/logging-log4j2/pull/3677
--
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...@lo
ppkarwasz commented on issue #3706:
URL:
https://github.com/apache/logging-log4j2/issues/3706#issuecomment-2933838484
Hi @verjan-isencia,
Thank you for reporting this issue.
This appears to be a composite problem caused by two factors:
1. In version `2.23.0`, we introduc
ppkarwasz closed issue #366: Lock Antora dependencies
URL: https://github.com/apache/logging-parent/issues/366
--
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
ppkarwasz commented on PR #389:
URL: https://github.com/apache/logging-parent/pull/389#issuecomment-2936742188
I forgot to mention that I deployed the same solution in
[`sbom-enforcer/sbom-enforcer`](https://github.com/sbom-enforcer/sbom-enforcer)
a couple of weeks ago and it seems to work
vy commented on code in PR #401:
URL: https://github.com/apache/logging-parent/pull/401#discussion_r2124649478
##
.github/workflows/deploy-release-reusable.yaml:
##
@@ -203,13 +203,8 @@ jobs:
- name: Stage distribution attachments
Review Comment:
```suggestion
vy commented on issue #400:
URL: https://github.com/apache/logging-parent/issues/400#issuecomment-2936723439
For the record, 769fd9810 uses `deploy:deploy` and only that, since it wants
to execute _only_ that goal of that particular plugin. I see #401 doesn't even
need any deployments, whic
vy commented on PR #389:
URL: https://github.com/apache/logging-parent/pull/389#issuecomment-2936943918
This PR
1. adds net 260 lines,
2. uses a plugin whose [README states
that](https://github.com/maveniverse/mimir/blob/0a7f04f576ae18109e7cac6a55d3dc29bb034708/README.md#L9)
rschmitt opened a new pull request, #3708:
URL: https://github.com/apache/logging-log4j2/pull/3708
Bumps
[com.fasterxml.jackson:jackson-bom](https://github.com/FasterXML/jackson-bom)
from 2.18.3 to 2.19.0.
-
[Commits](https://github.com/FasterXML/jackson-bom/compare/jackson-bom-2.18.3..
github-actions[bot] commented on PR #3708:
URL: https://github.com/apache/logging-log4j2/pull/3708#issuecomment-2937146993
Job
Requested goals
Build Tool Version
Build Outcome
Build Scan®
build-
arnosinghal opened a new issue, #3709:
URL: https://github.com/apache/logging-log4j2/issues/3709
## Description
[A clear and concise description of what the bug is.]
## Configuration
**Version:** [Log4j version]
**Operating system:** [OS and version]
**JDK:*
arnosinghal commented on issue #3709:
URL:
https://github.com/apache/logging-log4j2/issues/3709#issuecomment-2938473206
My Instagram account me 10k followers kr
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL
ppkarwasz closed issue #400: Creation of binary distribution fails
URL: https://github.com/apache/logging-parent/issues/400
--
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 u
ppkarwasz merged PR #401:
URL: https://github.com/apache/logging-parent/pull/401
--
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.
ppkarwasz closed issue #3709: 10k followers
URL: https://github.com/apache/logging-log4j2/issues/3709
--
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: no
gdziadkiewicz commented on issue #250:
URL:
https://github.com/apache/logging-log4net/issues/250#issuecomment-2938772262
Hi @maedula Yes, I reproduced the error and linked it to my changes. Thanks
for the details! Work on fix is in progress.
--
This is an automated message from the Apach
vy commented on PR #3677:
URL: https://github.com/apache/logging-log4j2/pull/3677#issuecomment-2934025196
@ppkarwasz, applied your suggestions in 0ee4732de79.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL abo
ppkarwasz merged PR #191:
URL: https://github.com/apache/logging-log4j-tools/pull/191
--
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-unsu
ppkarwasz merged PR #190:
URL: https://github.com/apache/logging-log4j-tools/pull/190
--
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-unsu
ppkarwasz closed issue #135: log4j-docgen: Missing `additivity` attribute for
LoggerConfig
URL: https://github.com/apache/logging-log4j-tools/issues/135
--
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
verjan-isencia commented on issue #3706:
URL:
https://github.com/apache/logging-log4j2/issues/3706#issuecomment-2934674703
I have been debugging the problem in our OSGI platform, and the problem
seems to be with the classloader used at the moment the static variable in
DisruptUtil is initi
23 matches
Mail list logo
