dfa1 commented on a change in pull request #770:
URL: https://github.com/apache/logging-log4j2/pull/770#discussion_r830335776
##
File path:
log4j-slf4j-impl/src/main/java/org/apache/logging/slf4j/Log4jMarkerFactory.java
##
@@ -113,26 +125,18 @@ public boolean exists(final Stri
dfa1 commented on a change in pull request #770:
URL: https://github.com/apache/logging-log4j2/pull/770#discussion_r830338691
##
File path:
log4j-slf4j-impl/src/main/java/org/apache/logging/slf4j/Log4jMarkerFactory.java
##
@@ -113,26 +125,18 @@ public boolean exists(final Stri
dfa1 commented on a change in pull request #770:
URL: https://github.com/apache/logging-log4j2/pull/770#discussion_r830338691
##
File path:
log4j-slf4j-impl/src/main/java/org/apache/logging/slf4j/Log4jMarkerFactory.java
##
@@ -113,26 +125,18 @@ public boolean exists(final Stri
dfa1 commented on a change in pull request #770:
URL: https://github.com/apache/logging-log4j2/pull/770#discussion_r830338691
##
File path:
log4j-slf4j-impl/src/main/java/org/apache/logging/slf4j/Log4jMarkerFactory.java
##
@@ -113,26 +125,18 @@ public boolean exists(final Stri
dfa1 commented on a change in pull request #770:
URL: https://github.com/apache/logging-log4j2/pull/770#discussion_r830331326
##
File path:
log4j-slf4j-impl/src/main/java/org/apache/logging/slf4j/Log4jMarkerFactory.java
##
@@ -113,26 +125,18 @@ public boolean exists(final Stri
carterkozak commented on a change in pull request #770:
URL: https://github.com/apache/logging-log4j2/pull/770#discussion_r830357475
##
File path:
log4j-slf4j-impl/src/main/java/org/apache/logging/slf4j/Log4jMarkerFactory.java
##
@@ -113,26 +125,18 @@ public boolean exists(fin
carterkozak commented on a change in pull request #770:
URL: https://github.com/apache/logging-log4j2/pull/770#discussion_r830364137
##
File path:
log4j-slf4j-impl/src/main/java/org/apache/logging/slf4j/Log4jMarkerFactory.java
##
@@ -113,26 +125,18 @@ public boolean exists(fin
rgoers commented on a change in pull request #804:
URL: https://github.com/apache/logging-log4j2/pull/804#discussion_r830447038
##
File path:
log4j-api/src/main/java/org/apache/logging/log4j/util/ServiceLoaderUtil.java
##
@@ -110,28 +139,64 @@ private ServiceLoaderUtil() {
rgoers commented on a change in pull request #804:
URL: https://github.com/apache/logging-log4j2/pull/804#discussion_r830447038
##
File path:
log4j-api/src/main/java/org/apache/logging/log4j/util/ServiceLoaderUtil.java
##
@@ -110,28 +139,64 @@ private ServiceLoaderUtil() {
rgoers commented on a change in pull request #804:
URL: https://github.com/apache/logging-log4j2/pull/804#discussion_r830447038
##
File path:
log4j-api/src/main/java/org/apache/logging/log4j/util/ServiceLoaderUtil.java
##
@@ -110,28 +139,64 @@ private ServiceLoaderUtil() {
rgoers commented on a change in pull request #804:
URL: https://github.com/apache/logging-log4j2/pull/804#discussion_r830447038
##
File path:
log4j-api/src/main/java/org/apache/logging/log4j/util/ServiceLoaderUtil.java
##
@@ -110,28 +139,64 @@ private ServiceLoaderUtil() {
rgoers commented on pull request #799:
URL: https://github.com/apache/logging-log4j2/pull/799#issuecomment-1072953796
This change would cause our RAT check to fail, would not match ASF
guidelines documented at https://www.apache.org/legal/src-headers.html, and as
Gary noted the URL is inva
rgoers closed pull request #799:
URL: https://github.com/apache/logging-log4j2/pull/799
--
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: notificati
rgoers commented on pull request #770:
URL: https://github.com/apache/logging-log4j2/pull/770#issuecomment-1072954499
@dfa1 In your comment above you said you do have a use case (one would hope
so for you to be implementing this) but you didn't explain your use case. All
you really said is
dfa1 commented on a change in pull request #770:
URL: https://github.com/apache/logging-log4j2/pull/770#discussion_r830449257
##
File path:
log4j-slf4j-impl/src/main/java/org/apache/logging/slf4j/Log4jMarkerFactory.java
##
@@ -113,26 +125,18 @@ public boolean exists(final Stri
dfa1 edited a comment on pull request #770:
URL: https://github.com/apache/logging-log4j2/pull/770#issuecomment-1072958711
@rgoers yes, of course :-) Let me try to explain clearly: in
https://www.six-group.com/ there is an internal requirement to use a structured
logging format (called un
dfa1 commented on pull request #770:
URL: https://github.com/apache/logging-log4j2/pull/770#issuecomment-1072958711
@rgoers yes, of course :-) Let me try to explain clearly: at @SIX-Group we
have an internal requirement to use a structured logging format (called unified
log event) for all
dfa1 edited a comment on pull request #770:
URL: https://github.com/apache/logging-log4j2/pull/770#issuecomment-1072958711
@rgoers yes, of course :-) Let me try to explain clearly: in
https://www.six-group.com/ there is an internal requirement to use a structured
logging format (called un
dfa1 edited a comment on pull request #770:
URL: https://github.com/apache/logging-log4j2/pull/770#issuecomment-1072958711
@rgoers yes, of course :-) Let me try to explain clearly: in
https://www.six-group.com/ there is an internal requirement to use a structured
logging format (called un
dfa1 commented on a change in pull request #770:
URL: https://github.com/apache/logging-log4j2/pull/770#discussion_r830456338
##
File path:
log4j-slf4j-impl/src/main/java/org/apache/logging/slf4j/Log4jMarkerFactory.java
##
@@ -113,26 +125,18 @@ public boolean exists(final Stri
dfa1 commented on a change in pull request #770:
URL: https://github.com/apache/logging-log4j2/pull/770#discussion_r830456338
##
File path:
log4j-slf4j-impl/src/main/java/org/apache/logging/slf4j/Log4jMarkerFactory.java
##
@@ -113,26 +125,18 @@ public boolean exists(final Stri
dfa1 commented on a change in pull request #770:
URL: https://github.com/apache/logging-log4j2/pull/770#discussion_r830457264
##
File path:
log4j-slf4j-impl/src/main/java/org/apache/logging/slf4j/Log4jMarkerFactory.java
##
@@ -113,26 +125,18 @@ public boolean exists(final Stri
rgoers commented on pull request #770:
URL: https://github.com/apache/logging-log4j2/pull/770#issuecomment-1072974525
Ok. So your big mistake here is trying to do this with the SLF4J API. It
wasn't designed to support structured event logging. I fought for that years
ago and gave up and th
rgoers edited a comment on pull request #770:
URL: https://github.com/apache/logging-log4j2/pull/770#issuecomment-1072974525
Ok. So your big mistake here is trying to do this with the SLF4J API. It
wasn't designed to support structured event logging. I fought for that years
ago and gave up
ppkarwasz commented on a change in pull request #804:
URL: https://github.com/apache/logging-log4j2/pull/804#discussion_r830463798
##
File path:
log4j-api/src/main/java/org/apache/logging/log4j/util/ServiceLoaderUtil.java
##
@@ -110,28 +139,64 @@ private ServiceLoaderUtil() {
rgoers edited a comment on pull request #770:
URL: https://github.com/apache/logging-log4j2/pull/770#issuecomment-1072974525
Ok. So your big mistake here is trying to do this with the SLF4J API. It
wasn't designed to support structured event logging. I fought for that years
ago and gave up
garydgregory commented on pull request #770:
URL: https://github.com/apache/logging-log4j2/pull/770#issuecomment-1072998257
I have a product at work that does almost exactly what @rgoers describes, it
works great, it's clean, and easy enough to understand. I encourage you as well
to move t
carterkozak commented on a change in pull request #770:
URL: https://github.com/apache/logging-log4j2/pull/770#discussion_r830479861
##
File path:
log4j-slf4j-impl/src/main/java/org/apache/logging/slf4j/Log4jMarkerFactory.java
##
@@ -113,26 +125,18 @@ public boolean exists(fin
rgoers commented on a change in pull request #804:
URL: https://github.com/apache/logging-log4j2/pull/804#discussion_r830502914
##
File path:
log4j-api/src/main/java/org/apache/logging/log4j/util/ServiceLoaderUtil.java
##
@@ -110,28 +139,64 @@ private ServiceLoaderUtil() {
rgoers commented on a change in pull request #804:
URL: https://github.com/apache/logging-log4j2/pull/804#discussion_r830502914
##
File path:
log4j-api/src/main/java/org/apache/logging/log4j/util/ServiceLoaderUtil.java
##
@@ -110,28 +139,64 @@ private ServiceLoaderUtil() {
dfa1 commented on pull request #770:
URL: https://github.com/apache/logging-log4j2/pull/770#issuecomment-1073047035
@rgoers @garydgregory thank you for the feedback ;)
Actually we already have a lot of internal libraries and frameworks written
against `slf4j-api`, and we do the actua
dfa1 commented on pull request #770:
URL: https://github.com/apache/logging-log4j2/pull/770#issuecomment-1073049642
@rgoers @carterkozak @garydgregory
*Current state*
- this PR is implementing the SLF4J's contract is a reasonable way (my
humble opinion)
- test coverage is
dfa1 edited a comment on pull request #770:
URL: https://github.com/apache/logging-log4j2/pull/770#issuecomment-1073049642
@rgoers @carterkozak @garydgregory
*Current state*
- this PR is implementing the SLF4J's contract in a reasonable way (my
humble opinion)
- test cove
rgoers commented on pull request #770:
URL: https://github.com/apache/logging-log4j2/pull/770#issuecomment-1073168934
@dfa1 I do understand your dilemma. You already have existing code that has
implemented this in the only way possible using SLF4J, which is a hack,
However, I have a real p
rgoers edited a comment on pull request #770:
URL: https://github.com/apache/logging-log4j2/pull/770#issuecomment-1073168934
@dfa1 I do understand your dilemma. You already have existing code that has
implemented this in the only way possible using SLF4J, which is a hack,
However, I have a
dfa1 commented on pull request #770:
URL: https://github.com/apache/logging-log4j2/pull/770#issuecomment-1073193347
@rgoers thanks for yours the honest feedback! :) Maintaining my own fork(s)
of SLF4J is what I wanted to avoid by proposing this PR!
After this long discussion, I reali
dfa1 edited a comment on pull request #770:
URL: https://github.com/apache/logging-log4j2/pull/770#issuecomment-1073193347
@rgoers thanks for yours the honest feedback! :) Maintaining my own fork(s)
of SLF4J is what I wanted to avoid by proposing this PR... I don't want to go
there!
rgoers commented on pull request #770:
URL: https://github.com/apache/logging-log4j2/pull/770#issuecomment-1073201000
That would be back to the same thing. Now you would have getMarker returning
a detached marker. If I thought detached markers were a good idea then
detachedMarker would be
ppkarwasz commented on a change in pull request #770:
URL: https://github.com/apache/logging-log4j2/pull/770#discussion_r830645307
##
File path:
log4j-slf4j-impl/src/main/java/org/apache/logging/slf4j/Log4jMarkerFactory.java
##
@@ -36,9 +38,11 @@
private static final Logg
dfa1 commented on pull request #770:
URL: https://github.com/apache/logging-log4j2/pull/770#issuecomment-1073293922
@rgoers I'm already using public ctor in `Log4jMarker`: but in order to do
that I need to "override" the code coming from log4j binding and now my
application are sensitive t
dfa1 commented on a change in pull request #770:
URL: https://github.com/apache/logging-log4j2/pull/770#discussion_r830646927
##
File path:
log4j-slf4j-impl/src/main/java/org/apache/logging/slf4j/Log4jMarkerFactory.java
##
@@ -36,9 +38,11 @@
private static final Logger LO
dfa1 commented on a change in pull request #770:
URL: https://github.com/apache/logging-log4j2/pull/770#discussion_r830646927
##
File path:
log4j-slf4j-impl/src/main/java/org/apache/logging/slf4j/Log4jMarkerFactory.java
##
@@ -36,9 +38,11 @@
private static final Logger LO
dfa1 commented on a change in pull request #770:
URL: https://github.com/apache/logging-log4j2/pull/770#discussion_r830646927
##
File path:
log4j-slf4j-impl/src/main/java/org/apache/logging/slf4j/Log4jMarkerFactory.java
##
@@ -36,9 +38,11 @@
private static final Logger LO
ppkarwasz opened a new pull request #806:
URL: https://github.com/apache/logging-log4j2/pull/806
Replaces an invalid `SSLContext` algorithm name with Log4j's default and
adds unit tests.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on
jvz merged pull request #744:
URL: https://github.com/apache/logging-log4j2/pull/744
--
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
garydgregory commented on a change in pull request #806:
URL: https://github.com/apache/logging-log4j2/pull/806#discussion_r830679706
##
File path:
log4j-core/src/main/java/org/apache/logging/log4j/core/net/ssl/AbstractKeyStoreConfiguration.java
##
@@ -33,6 +33,8 @@
* Config
garydgregory commented on pull request #806:
URL: https://github.com/apache/logging-log4j2/pull/806#issuecomment-1073371162
Hi @ppkarwasz
Do we want to test that we are creating a TLS connection instead of some
older protocol version?
--
This is an automated message from the Apache G
ppkarwasz commented on pull request #806:
URL: https://github.com/apache/logging-log4j2/pull/806#issuecomment-1073376320
@garydgregory: that test could fail, since the allowed protocols depend upon
the `java.security` configuration file of the JVM. Setting
`jdk.tls.disabledAlgorithms` to a
ppkarwasz edited a comment on pull request #806:
URL: https://github.com/apache/logging-log4j2/pull/806#issuecomment-1073376320
@garydgregory: that test could fail, since the allowed protocols depend upon
the `java.security` configuration file of the JVM. Setting
`jdk.tls.disabledAlgorithm
vy commented on a change in pull request #797:
URL: https://github.com/apache/logging-log4j2/pull/797#discussion_r830901725
##
File path:
log4j-layout-template-json/src/main/java/org/apache/logging/log4j/layout/template/json/resolver/MessageResolver.java
##
@@ -134,7 +134,10 @
vy commented on a change in pull request #797:
URL: https://github.com/apache/logging-log4j2/pull/797#discussion_r830911702
##
File path:
log4j-layout-template-json/src/main/java/org/apache/logging/log4j/layout/template/json/resolver/MessageResolver.java
##
@@ -134,7 +134,10 @
vy merged pull request #797:
URL: https://github.com/apache/logging-log4j2/pull/797
--
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-
vy commented on pull request #805:
URL: https://github.com/apache/logging-log4j2/pull/805#issuecomment-1073770054
Thanks for the heads up @Suji04! I've applied your changes in 6f282e6.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to
ppkarwasz commented on a change in pull request #804:
URL: https://github.com/apache/logging-log4j2/pull/804#discussion_r831575308
##
File path:
log4j-api/src/main/java/org/apache/logging/log4j/util/ServiceLoaderUtil.java
##
@@ -110,28 +78,73 @@ private ServiceLoaderUtil() {
rm5248 commented on pull request #108:
URL: https://github.com/apache/logging-log4cxx/pull/108#issuecomment-1074482366
> For some reason `timebasedrollingtest` failed once for me, but not on
subsequent 5 executions. So things seem to be fine.
That is likely due to how that test works
rm5248 merged pull request #108:
URL: https://github.com/apache/logging-log4cxx/pull/108
--
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: notificat
ppkarwasz commented on a change in pull request #804:
URL: https://github.com/apache/logging-log4j2/pull/804#discussion_r831826513
##
File path:
log4j-api/src/test/java/org/apache/logging/log4j/util/ServiceLoaderUtilTest.java
##
@@ -86,42 +85,4 @@ public void testBrokenService
ppkarwasz commented on a change in pull request #804:
URL: https://github.com/apache/logging-log4j2/pull/804#discussion_r831830675
##
File path:
log4j-api/src/main/java/org/apache/logging/log4j/util/ServiceLoaderUtil.java
##
@@ -110,28 +135,64 @@ private ServiceLoaderUtil() {
ppkarwasz commented on pull request #804:
URL: https://github.com/apache/logging-log4j2/pull/804#issuecomment-1074844988
After several fixes, this should work now. A summary of changes:
- I removed `LoaderServiceUtil#getService` that I introduced in a previous
commit, since it's logi
ppkarwasz merged pull request #806:
URL: https://github.com/apache/logging-log4j2/pull/806
--
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: notific
jvz commented on pull request #804:
URL: https://github.com/apache/logging-log4j2/pull/804#issuecomment-1075350519
> * OSGI support was also removed from `LoaderServiceUtil`, because it uses
an artifact (`osgi-resource-locator`) that seems to be abandoned (it is still
supported by JAXB API
ppkarwasz opened a new pull request #807:
URL: https://github.com/apache/logging-log4j2/pull/807
Log4j 1.x always used the BSD syslog layout, but allowed for an internal
layout to specify the _MESSAGE_ format.
This PR adds a variant of the Log4j 2.x `SyslogLayout`, that emulates Log4
dfa1 commented on pull request #770:
URL: https://github.com/apache/logging-log4j2/pull/770#issuecomment-1079376882
@rgoers tried also your last suggestion too:
> You are free to use ServiceLoader to locate the SLF4J Service Provider and
get the Marker factory and then create Markers
jvz opened a new pull request #808:
URL: https://github.com/apache/logging-log4j2/pull/808
This allows for a ConfigurationFactory binding to be registered as well as
generally participate in dependency injection.
Signed-off-by: Matt Sicker
--
This is an automated message from the
jvz commented on a change in pull request #808:
URL: https://github.com/apache/logging-log4j2/pull/808#discussion_r835695608
##
File path:
log4j-core/src/main/java/org/apache/logging/log4j/core/config/ConfigurationFactory.java
##
@@ -137,71 +119,15 @@ public ConfigurationFacto
grobmeier merged pull request #23:
URL: https://github.com/apache/logging-log4j-kotlin/pull/23
--
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
jvz merged pull request #808:
URL: https://github.com/apache/logging-log4j2/pull/808
--
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
jvz commented on pull request #775:
URL: https://github.com/apache/logging-log4j2/pull/775#issuecomment-1080106923
I'm going to merge this as-is. We can figure out how to integrate JSON
parsing with PropertiesUtil later.
--
This is an automated message from the Apache Git Service.
To res
jvz merged pull request #775:
URL: https://github.com/apache/logging-log4j2/pull/775
--
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
vy commented on a change in pull request #775:
URL: https://github.com/apache/logging-log4j2/pull/775#discussion_r836108757
##
File path:
log4j-core-test/src/test/java/org/apache/logging/log4j/core/util/JsonReaderTest.java
##
@@ -375,6 +376,11 @@ public void test_nesting() {
garydgregory commented on a change in pull request #683:
URL: https://github.com/apache/logging-log4j2/pull/683#discussion_r836407990
##
File path: log4j-core/revapi.json
##
@@ -128,6 +128,25 @@
"annotation":
"@org.apache.logging.log4j.core.config.plugins.PluginFactor
atulpendse commented on a change in pull request #683:
URL: https://github.com/apache/logging-log4j2/pull/683#discussion_r836438381
##
File path: log4j-core/revapi.json
##
@@ -128,6 +128,25 @@
"annotation":
"@org.apache.logging.log4j.core.config.plugins.PluginFactory"
atulpendse commented on a change in pull request #683:
URL: https://github.com/apache/logging-log4j2/pull/683#discussion_r836438381
##
File path: log4j-core/revapi.json
##
@@ -128,6 +128,25 @@
"annotation":
"@org.apache.logging.log4j.core.config.plugins.PluginFactory"
garydgregory commented on a change in pull request #683:
URL: https://github.com/apache/logging-log4j2/pull/683#discussion_r836761436
##
File path:
log4j-core/src/main/java/org/apache/logging/log4j/core/appender/SyslogAppender.java
##
@@ -393,7 +408,8 @@ protected SyslogAppend
garydgregory commented on a change in pull request #683:
URL: https://github.com/apache/logging-log4j2/pull/683#discussion_r836762447
##
File path:
log4j-core/src/main/java/org/apache/logging/log4j/core/layout/Rfc5424Layout.java
##
@@ -627,7 +608,8 @@ public static Rfc5424Layo
garydgregory commented on pull request #683:
URL: https://github.com/apache/logging-log4j2/pull/683#issuecomment-1081036428
Hello @atulpendse
In general, you want to avoid breaking binary compatibility, so that means
not editing public and protected type names and method signatures. Th
atulpendse commented on a change in pull request #683:
URL: https://github.com/apache/logging-log4j2/pull/683#discussion_r837103493
##
File path:
log4j-core/src/main/java/org/apache/logging/log4j/core/appender/SyslogAppender.java
##
@@ -393,7 +408,8 @@ protected SyslogAppender
astappiev commented on pull request #745:
URL: https://github.com/apache/logging-log4j2/pull/745#issuecomment-1081915601
Any progress on this or release date?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL ab
stefanvodita opened a new pull request #809:
URL: https://github.com/apache/logging-log4j2/pull/809
A race condition could appear when 2 threads were trying to create the
same directory. Both would check that the directory did not exist, then
one would create the directory and the othe
ppkarwasz commented on a change in pull request #809:
URL: https://github.com/apache/logging-log4j2/pull/809#discussion_r837669556
##
File path:
log4j-core/src/test/java/org/apache/logging/log4j/core/util/FileUtilsTest.java
##
@@ -78,4 +86,56 @@ public void
testFileFromUriWit
ppkarwasz commented on a change in pull request #683:
URL: https://github.com/apache/logging-log4j2/pull/683#discussion_r837730815
##
File path:
log4j-core/src/main/java/org/apache/logging/log4j/core/layout/Rfc5424Layout.java
##
@@ -92,11 +97,12 @@
*/
public static
ppkarwasz commented on a change in pull request #683:
URL: https://github.com/apache/logging-log4j2/pull/683#discussion_r837730815
##
File path:
log4j-core/src/main/java/org/apache/logging/log4j/core/layout/Rfc5424Layout.java
##
@@ -92,11 +97,12 @@
*/
public static
ppkarwasz commented on pull request #745:
URL: https://github.com/apache/logging-log4j2/pull/745#issuecomment-1082395718
@astappiev,
As far as I am concerned, this could end up in the next release. You can
check if it works for you.
--
This is an automated message from the Apache Git
jvz commented on a change in pull request #775:
URL: https://github.com/apache/logging-log4j2/pull/775#discussion_r838011000
##
File path:
log4j-core-test/src/test/java/org/apache/logging/log4j/core/util/JsonReaderTest.java
##
@@ -375,6 +376,11 @@ public void test_nesting() {
stefanvodita commented on a change in pull request #809:
URL: https://github.com/apache/logging-log4j2/pull/809#discussion_r838804651
##
File path:
log4j-core/src/test/java/org/apache/logging/log4j/core/util/FileUtilsTest.java
##
@@ -78,4 +86,56 @@ public void
testFileFromUri
ppkarwasz merged pull request #809:
URL: https://github.com/apache/logging-log4j2/pull/809
--
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: notific
ppkarwasz commented on pull request #809:
URL: https://github.com/apache/logging-log4j2/pull/809#issuecomment-1083632089
@stefanvodita,
Thank you for your contribution.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and u
garydgregory commented on pull request #807:
URL: https://github.com/apache/logging-log4j2/pull/807#issuecomment-1084406409
@rgoers
Ping: Does this look good to you?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use
ppkarwasz commented on pull request #807:
URL: https://github.com/apache/logging-log4j2/pull/807#issuecomment-1084513836
I added a third parameter to `DatePatternConverter`, so that I can use it
with a fixed English locale. I am not documenting it in the manual, because for
now it does not
ppkarwasz edited a comment on pull request #807:
URL: https://github.com/apache/logging-log4j2/pull/807#issuecomment-1084513836
I added a third parameter to `DatePatternConverter`, so that I can use it
with a fixed English locale. I am not documenting it in the manual, because for
now it d
loganaden opened a new pull request #810:
URL: https://github.com/apache/logging-log4j2/pull/810
See details: https://tanzu.vmware.com/security/cve-2022-22965
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL ab
garydgregory commented on pull request #810:
URL: https://github.com/apache/logging-log4j2/pull/810#issuecomment-1084927755
Dependabot takes care of this for us.
--
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 merged pull request #807:
URL: https://github.com/apache/logging-log4j2/pull/807
--
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: notific
controllerface opened a new pull request #811:
URL: https://github.com/apache/logging-log4j2/pull/811
SLF4JServiceProvider defines the `getRequestedApiVersion()` method, but this
class has a typo, the method is incorrectly named `getRequesteApiVersion()`
which causes the following error me
ppkarwasz commented on pull request #811:
URL: https://github.com/apache/logging-log4j2/pull/811#issuecomment-1085806732
Hello @controllerface,
That is not a typo, it is the method name SLF4J 1.8.x uses: see
[LOG4J2-3370](https://issues.apache.org/jira/browse/LOG4J2-3370).
--
This is
ppkarwasz edited a comment on pull request #811:
URL: https://github.com/apache/logging-log4j2/pull/811#issuecomment-1085806732
Hello @controllerface,
That is not a typo, it is the method name SLF4J 1.8.x uses: see
[LOG4J2-3370](https://issues.apache.org/jira/browse/LOG4J2-3370)
You a
controllerface commented on pull request #811:
URL: https://github.com/apache/logging-log4j2/pull/811#issuecomment-1085826047
ok. wow. that's just... really confusing. I will close the PR.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log o
controllerface closed pull request #811:
URL: https://github.com/apache/logging-log4j2/pull/811
--
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
clara0 opened a new pull request #812:
URL: https://github.com/apache/logging-log4j2/pull/812
https://issues.apache.org/jira/browse/LOG4J2-3462
--
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 th
ppkarwasz opened a new pull request #813:
URL: https://github.com/apache/logging-log4j2/pull/813
Forwards the `addAppender`, `callAppenders`, `getAllAppenders` and
`getAppender` calls the the corresponding Log4j 2.x objects if Log4j 2.x Core
is present.
The `getAllAppenders` method
5201 - 5300 of 7264 matches
Mail list logo