github-actions[bot] merged PR #100:
URL: https://github.com/apache/logging-log4j-tools/pull/100
--
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:
dependabot[bot] opened a new pull request, #100:
URL: https://github.com/apache/logging-log4j-tools/pull/100
Bumps [org.assertj:assertj-core](https://github.com/assertj/assertj) from
3.25.1 to 3.25.2.
Release notes
Sourced from
dependabot[bot] commented on PR #101:
URL:
https://github.com/apache/logging-log4j-samples/pull/101#issuecomment-1909418784
OK, I won't notify you again about this release, but will get in touch when
a new version is available. If you'd rather skip all updates until the next
major or
ppkarwasz closed pull request #101: Bump org.apache.logging.log4j:log4j-bom
from 0.0.0-SNAPSHOT to 3.0.0-beta1
URL: https://github.com/apache/logging-log4j-samples/pull/101
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use
swebb2066 commented on PR #338:
URL: https://github.com/apache/logging-log4cxx/pull/338#issuecomment-1909364158
The [updated staging web
site](https://logging.staged.apache.org/log4cxx/latest_stable/usage-overview.html)
is available for review.
--
This is an automated message from the
swebb2066 opened a new pull request, #338:
URL: https://github.com/apache/logging-log4cxx/pull/338
The log4cxx 1.2 web site does not have reference documentation for
DOMConfigurator.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to
swebb2066 merged PR #337:
URL: https://github.com/apache/logging-log4cxx/pull/337
--
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:
dependabot[bot] opened a new pull request, #110:
URL: https://github.com/apache/logging-log4j-samples/pull/110
Bumps [org.assertj:assertj-bom](https://github.com/assertj/assertj) from
3.25.1 to 3.25.2.
Release notes
Sourced from
swebb2066 commented on PR #337:
URL: https://github.com/apache/logging-log4cxx/pull/337#issuecomment-1909148787
The new benchmarks for Windos are:
| Benchmark | Time | CPU | Iterations |
| | - | | |
| Testing disabled logging request | 2.96 ns |
beatngu13 commented on PR #658:
URL: https://github.com/apache/logging-log4j2/pull/658#issuecomment-1909041730
Hey @vy & @garydgregory,
JUnit Pioneer maintainer here. ✌️ I know this PR is old and the problem it
was trying to solve might not relevant anymore, but regarding:
>
ppkarwasz opened a new pull request, #2242:
URL: https://github.com/apache/logging-log4j2/pull/2242
This PR removes all occurences of `instanceof Async*` that might prevent the
separation of the async support.
The removal requires a couple of new API methods and binary incompatible
github-actions[bot] merged PR #16:
URL: https://github.com/apache/logging-log4j-jakarta/pull/16
--
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:
ppkarwasz commented on PR #2230:
URL: https://github.com/apache/logging-log4j2/pull/2230#issuecomment-1908834695
Part of #2163
--
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
ppkarwasz opened a new pull request, #2241:
URL: https://github.com/apache/logging-log4j2/pull/2241
This PR moves the `AsyncLogger` and `AsyncLoggerConfig` classes from
`log4j-core` to a separate `log4j-async-logger` artifact. It is part of #2163.
- [ ] move tests to
ppkarwasz merged PR #2230:
URL: https://github.com/apache/logging-log4j2/pull/2230
--
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:
github-actions[bot] merged PR #81:
URL: https://github.com/apache/logging-log4j-transform/pull/81
--
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:
grobmeier closed issue #2016: [MS7] Branch `main` overhaul #2
URL: https://github.com/apache/logging-log4j2/issues/2016
--
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
grobmeier commented on issue #2016:
URL:
https://github.com/apache/logging-log4j2/issues/2016#issuecomment-1908768234
completed
--
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
dependabot[bot] opened a new pull request, #81:
URL: https://github.com/apache/logging-log4j-transform/pull/81
Bumps [org.assertj:assertj-core](https://github.com/assertj/assertj) from
3.25.1 to 3.25.2.
Release notes
Sourced from
ppkarwasz commented on issue #2238:
URL:
https://github.com/apache/logging-log4j2/issues/2238#issuecomment-1908748402
@jdgenerix,
After looking better at the code the native storage of
`DefaultThreadContextMap` is JDK's `Map`, so the only optimization possible is
to create an
ppkarwasz commented on code in PR #2230:
URL: https://github.com/apache/logging-log4j2/pull/2230#discussion_r1465405877
##
log4j-core/src/main/java/org/apache/logging/log4j/core/config/AbstractConfiguration.java:
##
@@ -1178,4 +1152,28 @@ public NanoClock getNanoClock() {
ppkarwasz commented on code in PR #2230:
URL: https://github.com/apache/logging-log4j2/pull/2230#discussion_r1465008485
##
log4j-core/src/main/java/org/apache/logging/log4j/core/config/AbstractConfiguration.java:
##
@@ -1178,4 +1152,28 @@ public NanoClock getNanoClock() {
ppkarwasz commented on code in PR #2230:
URL: https://github.com/apache/logging-log4j2/pull/2230#discussion_r1464991374
##
log4j-core/src/main/java/org/apache/logging/log4j/core/async/DisruptorConfiguration.java:
##
@@ -0,0 +1,132 @@
+/*
+ * Licensed to the Apache Software
ppkarwasz commented on code in PR #2230:
URL: https://github.com/apache/logging-log4j2/pull/2230#discussion_r1464974551
##
log4j-core/src/main/java/org/apache/logging/log4j/core/config/AbstractConfiguration.java:
##
@@ -732,12 +705,12 @@ protected void doConfigure() {
jdgenerix commented on issue #2238:
URL:
https://github.com/apache/logging-log4j2/issues/2238#issuecomment-1908102284
@ppkarwasz I'm sorry, i don't really see the optimzation you saw with
`ReadOnlyThreadContextMap`.
--
This is an automated message from the Apache Git Service.
To respond
vy commented on code in PR #2230:
URL: https://github.com/apache/logging-log4j2/pull/2230#discussion_r1464849027
##
log4j-core/src/main/java/org/apache/logging/log4j/core/config/AbstractConfiguration.java:
##
@@ -1178,4 +1152,28 @@ public NanoClock getNanoClock() {
public
vy commented on code in PR #2230:
URL: https://github.com/apache/logging-log4j2/pull/2230#discussion_r1464843982
##
log4j-core/src/main/java/org/apache/logging/log4j/core/config/AbstractConfiguration.java:
##
@@ -1178,4 +1152,28 @@ public NanoClock getNanoClock() {
public
ppkarwasz commented on code in PR #2230:
URL: https://github.com/apache/logging-log4j2/pull/2230#discussion_r1464839041
##
log4j-core/src/main/java/org/apache/logging/log4j/core/config/AbstractConfiguration.java:
##
@@ -1178,4 +1152,28 @@ public NanoClock getNanoClock() {
ppkarwasz commented on code in PR #2230:
URL: https://github.com/apache/logging-log4j2/pull/2230#discussion_r1464828156
##
log4j-core/src/main/java/org/apache/logging/log4j/core/config/ConfigurationExtension.java:
##
@@ -0,0 +1,22 @@
+/*
+ * Licensed to the Apache Software
ppkarwasz commented on code in PR #2230:
URL: https://github.com/apache/logging-log4j2/pull/2230#discussion_r1464826082
##
log4j-core/src/main/java/org/apache/logging/log4j/core/config/AbstractConfiguration.java:
##
@@ -1178,4 +1152,28 @@ public NanoClock getNanoClock() {
vy commented on code in PR #2230:
URL: https://github.com/apache/logging-log4j2/pull/2230#discussion_r1464763541
##
log4j-core/src/main/java/org/apache/logging/log4j/core/config/AbstractConfiguration.java:
##
@@ -1178,4 +1152,28 @@ public NanoClock getNanoClock() {
public
github-actions[bot] closed pull request #2240: Bump actions/upload-artifact
from 4.2.0 to 4.3.0
URL: https://github.com/apache/logging-log4j2/pull/2240
--
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
github-actions[bot] closed pull request #2237: Bump
org.elasticsearch.client:elasticsearch-rest-high-level-client from 7.17.16 to
7.17.17
URL: https://github.com/apache/logging-log4j2/pull/2237
--
This is an automated message from the Apache Git Service.
To respond to the message, please
github-actions[bot] merged PR #2236:
URL: https://github.com/apache/logging-log4j2/pull/2236
--
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:
ppkarwasz commented on PR #2112:
URL: https://github.com/apache/logging-log4j2/pull/2112#issuecomment-1907892530
@Alanoudj,
The `log4j-api` version 2.23.0 artifact will be used by both Log4j Core
2.23.0 and Log4j Core 3.0.0-beta2, so the ETA for 2.23.0 is around end of
February.
ppkarwasz commented on issue #2232:
URL:
https://github.com/apache/logging-log4j2/issues/2232#issuecomment-1907882130
> In this instance I'm interacting with Log4j to programmatically disable
all logging (which I don't think is possible with only Slf4J). I'm guessing I
could/should switch
Alanoudj commented on PR #2112:
URL: https://github.com/apache/logging-log4j2/pull/2112#issuecomment-1907866862
Do you have any deadline for 2.23.0 version release?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
github-actions[bot] merged PR #110:
URL: https://github.com/apache/logging-parent/pull/110
--
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:
vy commented on PR #2239:
URL: https://github.com/apache/logging-log4j2/pull/2239#issuecomment-1907856814
@ppkarwasz, will do.
--
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
vy merged PR #2239:
URL: https://github.com/apache/logging-log4j2/pull/2239
--
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:
dependabot[bot] opened a new pull request, #110:
URL: https://github.com/apache/logging-parent/pull/110
Bumps [actions/upload-artifact](https://github.com/actions/upload-artifact)
from 4.2.0 to 4.3.0.
Release notes
Sourced from
ppkarwasz commented on issue #2238:
URL:
https://github.com/apache/logging-log4j2/issues/2238#issuecomment-1907818021
@jdgenerix,
Thank you for this report. Can you supply a PR to correct this?
--
This is an automated message from the Apache Git Service.
To respond to the message,
vy opened a new pull request, #2239:
URL: https://github.com/apache/logging-log4j2/pull/2239
(no comment)
--
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,
ppkarwasz opened a new issue, #2238:
URL: https://github.com/apache/logging-log4j2/issues/2238
### Discussed in https://github.com/apache/logging-log4j2/discussions/2235
Originally posted by **jdgenerix** January 24, 2024
The
vy closed issue #2232: Upgrading 2.21.1 to 2.22.0 causes compilation failure on
`BaselineIgnore`
URL: https://github.com/apache/logging-log4j2/issues/2232
--
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
big-andy-coates commented on issue #2232:
URL:
https://github.com/apache/logging-log4j2/issues/2232#issuecomment-1907779756
> -classFile
Adding `-classfile`, (not `-classFile`), does fix the issue. Many thanks,
--
This is an automated message from the Apache Git Service.
To
big-andy-coates commented on issue #2232:
URL:
https://github.com/apache/logging-log4j2/issues/2232#issuecomment-1907773867
> @big-andy-coates, a side note: Are you sure you need `log4j-core` at
compile-time? It should ideally be a `runtimeOnly` dependency. If that does not
work for you,
vy opened a new issue, #2234:
URL: https://github.com/apache/logging-log4j2/issues/2234
The issue was reported by @piecebook in
https://github.com/apache/logging-log4j2/discussions/2233 discussion.
--
This is an automated message from the Apache Git Service.
To respond to the message,
vy commented on issue #2232:
URL:
https://github.com/apache/logging-log4j2/issues/2232#issuecomment-1907638757
@big-andy-coates, a side note: Are you sure you need `log4j-core` at
compile-time? It should ideally be a `runtimeOnly` dependency. If that does not
work for you, I would like to
vy commented on issue #2232:
URL:
https://github.com/apache/logging-log4j2/issues/2232#issuecomment-1907633017
@big-andy-coates, I guess this is similar to the issue reported in #2144.
AFAIU, you are using
50 matches
Mail list logo
