dfa1 commented on pull request #770:
URL: https://github.com/apache/logging-log4j2/pull/770#issuecomment-1047476853
@garydgregory thank you for the review... please have a look now, I wrote
few unit tests
--
This is an automated message from the Apache Git Service.
To respond to the
[
https://issues.apache.org/jira/browse/LOG4J2-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17495819#comment-17495819
]
Barry Sham edited comment on LOG4J2-3410 at 2/22/22, 1:58 AM:
--
Dear
[
https://issues.apache.org/jira/browse/LOG4J2-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17495819#comment-17495819
]
Barry Sham commented on LOG4J2-3410:
Dear [~ggregory] and [~ppkarwasz],
We updated our testing repo
LeeGDavis commented on pull request #105:
URL: https://github.com/apache/logging-log4cxx/pull/105#issuecomment-1047317100
Thanks @rm5248. I'll give that a try. I'll see what I can do about a test
case too.
--
This is an automated message from the Apache Git Service.
To respond to
rm5248 commented on pull request #105:
URL: https://github.com/apache/logging-log4cxx/pull/105#issuecomment-1047304623
You could try using a vcpkg overlay to build a custom version of log4cxx.
See the [vcpkg
LeeGDavis commented on pull request #105:
URL: https://github.com/apache/logging-log4cxx/pull/105#issuecomment-1047299349
I think we're running into this issue after and upgrade to 0.12.1 from
0.11.0. Is there any way to tests this or what is currently in
rm5248 opened a new pull request #11:
URL: https://github.com/apache/logging-chainsaw/pull/11
Remove the hard dependency on log4j1.
General changes:
- Removed database stuff for the time being
- Created a new `ChainsawLoggingEvent` to be independent of log4j1
- Changed
garydgregory commented on a change in pull request #769:
URL: https://github.com/apache/logging-log4j2/pull/769#discussion_r811446174
##
File path:
log4j-slf4j-impl/src/main/java/org/apache/logging/slf4j/Log4jMDCAdapter.java
##
@@ -52,8 +52,7 @@ public void clear() {
}
dfa1 commented on a change in pull request #769:
URL: https://github.com/apache/logging-log4j2/pull/769#discussion_r811438451
##
File path:
log4j-slf4j-impl/src/main/java/org/apache/logging/slf4j/Log4jMDCAdapter.java
##
@@ -52,8 +52,7 @@ public void clear() {
}
dfa1 commented on a change in pull request #769:
URL: https://github.com/apache/logging-log4j2/pull/769#discussion_r811438451
##
File path:
log4j-slf4j-impl/src/main/java/org/apache/logging/slf4j/Log4jMDCAdapter.java
##
@@ -52,8 +52,7 @@ public void clear() {
}
garydgregory commented on pull request #770:
URL: https://github.com/apache/logging-log4j2/pull/770#issuecomment-1047241499
Hi @dfa1
Thank you for the PR.
You will need to add tests to this PR to prove the code does what you say it
does.
--
This is an automated message from the
dfa1 opened a new pull request #770:
URL: https://github.com/apache/logging-log4j2/pull/770
Hello all,
please accept this small patch from a long time user of log4j: it will
enable using log4j 2.x in several applications here at @six-group!
This proposal allows creating
garydgregory commented on a change in pull request #769:
URL: https://github.com/apache/logging-log4j2/pull/769#discussion_r811434361
##
File path:
log4j-slf4j-impl/src/main/java/org/apache/logging/slf4j/Log4jMDCAdapter.java
##
@@ -52,8 +52,7 @@ public void clear() {
}
[
https://issues.apache.org/jira/browse/LOG4J2-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17495763#comment-17495763
]
ASF subversion and git services commented on LOG4J2-3393:
-
Commit
[
https://issues.apache.org/jira/browse/LOG4J2-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17495764#comment-17495764
]
ASF subversion and git services commented on LOG4J2-3393:
-
Commit
dfa1 opened a new pull request #769:
URL: https://github.com/apache/logging-log4j2/pull/769
Minor cleanups in SLF4J bindings
Including removal of
[SLF4JLoggingException](https://github.com/apache/logging-log4j2/commit/d993a4faf17c1e5380e0eb87c02ee9d69318eb68)
--
This is an
ppkarwasz opened a new pull request #768:
URL: https://github.com/apache/logging-log4j2/pull/768
If a Builder fails due to a missing property, it return `null`. This
activates the fallback _"instantiate by class name"_ mechanism that will fail
with `NoClassDefFoundException` in the best
garydgregory commented on pull request #764:
URL: https://github.com/apache/logging-log4j2/pull/764#issuecomment-1047183989
@ppkarwasz
Thank you for your PR.
If you are looking for more fixes to investigate, please have a look at the
disabled tests in
garydgregory merged pull request #764:
URL: https://github.com/apache/logging-log4j2/pull/764
--
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:
[
https://issues.apache.org/jira/browse/LOG4J2-3407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17495733#comment-17495733
]
ASF subversion and git services commented on LOG4J2-3407:
-
Commit
ppkarwasz commented on a change in pull request #767:
URL: https://github.com/apache/logging-log4j2/pull/767#discussion_r811369316
##
File path:
log4j-api/src/main/java/org/apache/logging/log4j/util/SortedArrayStringMap.java
##
@@ -128,6 +128,21 @@
private boolean
garydgregory commented on a change in pull request #767:
URL: https://github.com/apache/logging-log4j2/pull/767#discussion_r811358091
##
File path:
log4j-api/src/main/java/org/apache/logging/log4j/util/SortedArrayStringMap.java
##
@@ -128,6 +128,21 @@
private boolean
[
https://issues.apache.org/jira/browse/LOG4J2-3407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary D. Gregory resolved LOG4J2-3407.
-
Fix Version/s: 2.17.2
Resolution: Fixed
[~kennymacleod.atl]
In git branch
garydgregory merged pull request #761:
URL: https://github.com/apache/logging-log4j2/pull/761
--
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:
[
https://issues.apache.org/jira/browse/LOG4J2-3407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17495621#comment-17495621
]
ASF subversion and git services commented on LOG4J2-3407:
-
Commit
[
https://issues.apache.org/jira/browse/LOG4J2-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary D. Gregory resolved LOG4J2-3410.
-
Fix Version/s: 2.17.2
Resolution: Fixed
Hi [~bcfsham] ,
Thank you for reporting
[
https://issues.apache.org/jira/browse/LOG4J2-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17495617#comment-17495617
]
ASF subversion and git services commented on LOG4J2-3410:
-
Commit
[
https://issues.apache.org/jira/browse/LOG4J2-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on LOG4J2-3410 started by Gary D. Gregory.
---
> Log4j 1.2 bridge throws a ClassCastException when logging a Map with
[
https://issues.apache.org/jira/browse/LOG4J2-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary D. Gregory reassigned LOG4J2-3410:
---
Assignee: Gary D. Gregory
> Log4j 1.2 bridge throws a ClassCastException when
[
https://issues.apache.org/jira/browse/LOG4J2-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary D. Gregory updated LOG4J2-3410:
Summary: Log4j 1.x Compatibility API - ClassCastException when logging a
Map with
[
https://issues.apache.org/jira/browse/LOG4J2-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary D. Gregory updated LOG4J2-3410:
Summary: Log4j 1.2 bridge throws a ClassCastException when logging a Map
with non-String
ppkarwasz commented on a change in pull request #767:
URL: https://github.com/apache/logging-log4j2/pull/767#discussion_r811231397
##
File path: log4j-1.2-api/src/main/java/org/apache/log4j/Category.java
##
@@ -309,15 +309,10 @@ private void fireRemoveAppenderEvent(final
ppkarwasz opened a new pull request #767:
URL: https://github.com/apache/logging-log4j2/pull/767
This PR provides a `MessageFactory` that decides the type of message based
on the runtime type of the logged object (cf.
[LOG4J2-3080](https://issues.apache.org/jira/browse/LOG4J2-3080)).
[
https://issues.apache.org/jira/browse/LOG4J2-3409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17495574#comment-17495574
]
Ralph Goers commented on LOG4J2-3409:
-
I had hoped it would have been out weeks ago, but after so
[
https://issues.apache.org/jira/browse/LOG4J2-3409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17495563#comment-17495563
]
alexander kravchik commented on LOG4J2-3409:
ok great news - do you have estimation when it
[
https://issues.apache.org/jira/browse/LOG4J2-3409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17495528#comment-17495528
]
Ralph Goers commented on LOG4J2-3409:
-
The thing is, once Flume 1.10.0 is released Log4J will
ruhulmus edited a comment on pull request #763:
URL: https://github.com/apache/logging-log4j2/pull/763#issuecomment-1046775984
> @ruhulmus If this is an example for people, showing them how to use Async
logging, then what would be the best place so that people can easily find it?
Maybe in
ruhulmus commented on pull request #763:
URL: https://github.com/apache/logging-log4j2/pull/763#issuecomment-1046775984
> @ruhulmus If this is an example for people, showing them how to use Async
logging, then what would be the best place so that people can easily find it?
Maybe in the
[
https://issues.apache.org/jira/browse/LOG4J2-3389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17495446#comment-17495446
]
Brian Antao commented on LOG4J2-3389:
-
It would be nice to have OnShutdownTriggeringPolicy be
[
https://issues.apache.org/jira/browse/LOG4J2-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17495444#comment-17495444
]
Piotr P. Karwasz commented on LOG4J2-3410:
--
To me it also seems like a bug in
dependabot[bot] closed pull request #2:
URL: https://github.com/apache/logging-parent/pull/2
--
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] commented on pull request #2:
URL: https://github.com/apache/logging-parent/pull/2#issuecomment-1046688982
Superseded by #4.
--
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
dependabot[bot] opened a new pull request #4:
URL: https://github.com/apache/logging-parent/pull/4
Bumps [apache](https://github.com/apache/maven-apache-parent) from 24 to 25.
Commits
See full diff in https://github.com/apache/maven-apache-parent/commits;>compare
view
[
https://issues.apache.org/jira/browse/LOG4J2-3409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17495413#comment-17495413
]
alexander kravchik commented on LOG4J2-3409:
Hi Matt & Ralph,
I opened the issue on log4j
Barry Sham created LOG4J2-3410:
--
Summary: Log4j 1.x Compatibility API - ClassCastException when
logging MultiKeyMap
Key: LOG4J2-3410
URL: https://issues.apache.org/jira/browse/LOG4J2-3410
Project: Log4j
vy merged pull request #766:
URL: https://github.com/apache/logging-log4j2/pull/766
--
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 pull request #750:
URL: https://github.com/apache/logging-log4j2/pull/750#issuecomment-1046619861
@garydgregory see #503 for some more context.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL
47 matches
Mail list logo
