vy commented on pull request #470:
URL: https://github.com/apache/logging-log4j2/pull/470#issuecomment-787803000
@jkozlowski, thanks so much for the contribution! Would you mind updating
the `changes.xml` too, please? That is,
```xml
OutputStreamManager does not clear buffer
jkozlowski commented on pull request #470:
URL: https://github.com/apache/logging-log4j2/pull/470#issuecomment-787872163
@vy should be done now
This is an automated message from the Apache Git Service.
To respond to the messa
jkozlowski commented on pull request #470:
URL: https://github.com/apache/logging-log4j2/pull/470#issuecomment-787941498
Hmm, there were merge conflicts, so I merged develop and now builds aren't
green; I wonder if it's an actual issue or a flake?
-
carterkozak commented on pull request #470:
URL: https://github.com/apache/logging-log4j2/pull/470#issuecomment-787966215
It looks like a build flake, I'll take care of the merge in the next hour
This is an automated message
carterkozak commented on pull request #470:
URL: https://github.com/apache/logging-log4j2/pull/470#issuecomment-788031443
@vy Yep, I've taken care of merging this :-)
This is an automated message from the Apache Git Service.
carterkozak closed pull request #470:
URL: https://github.com/apache/logging-log4j2/pull/470
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
vy opened a new pull request #471:
URL: https://github.com/apache/logging-log4j2/pull/471
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
vy commented on pull request #471:
URL: https://github.com/apache/logging-log4j2/pull/471#issuecomment-788212187
@rgoers, would you mind reviewing the changes, please? Note that I don't
create a new `HashSet` for each internal call, which has used to be the case.
According to tests, this s
carterkozak commented on a change in pull request #471:
URL: https://github.com/apache/logging-log4j2/pull/471#discussion_r585008161
##
File path:
log4j-api/src/main/java/org/apache/logging/log4j/message/ParameterFormatter.java
##
@@ -538,24 +536,28 @@ private static void appe
carterkozak commented on a change in pull request #471:
URL: https://github.com/apache/logging-log4j2/pull/471#discussion_r585008161
##
File path:
log4j-api/src/main/java/org/apache/logging/log4j/message/ParameterFormatter.java
##
@@ -538,24 +536,28 @@ private static void appe
Marcono1234 commented on a change in pull request #471:
URL: https://github.com/apache/logging-log4j2/pull/471#discussion_r585119540
##
File path:
log4j-api/src/main/java/org/apache/logging/log4j/message/ParameterFormatter.java
##
@@ -448,7 +450,7 @@ static String deepToString
vy commented on pull request #471:
URL: https://github.com/apache/logging-log4j2/pull/471#issuecomment-788765792
@carterkozak, would you mind skimming through the changes one last time,
please? If you approve, I am gonna merge this into `release-2.x` and will get
busy with porting it to `m
vy commented on a change in pull request #471:
URL: https://github.com/apache/logging-log4j2/pull/471#discussion_r585384100
##
File path:
log4j-api/src/main/java/org/apache/logging/log4j/message/ParameterFormatter.java
##
@@ -538,24 +536,28 @@ private static void appendArray(f
carterkozak commented on a change in pull request #471:
URL: https://github.com/apache/logging-log4j2/pull/471#discussion_r585530427
##
File path:
log4j-api/src/test/java/org/apache/logging/log4j/message/ParameterFormatterTest.java
##
@@ -180,13 +182,29 @@ public void testDeep
ams-tschoening commented on a change in pull request #53:
URL: https://github.com/apache/logging-log4cxx/pull/53#discussion_r585597348
##
File path: src/cmake/boost-fallback/boost-std-configuration.h.cmake
##
@@ -0,0 +1,94 @@
+#ifndef BOOST_STD_CONFIGURATION_H
+#define BOOST_ST
ams-tschoening commented on a change in pull request #53:
URL: https://github.com/apache/logging-log4cxx/pull/53#discussion_r585600144
##
File path: src/main/cpp/domconfigurator.cpp
##
@@ -331,10 +321,12 @@ void DOMConfigurator::parseErrorHandler(Pool& p,
AppenderMap& a
radut opened a new pull request #472:
URL: https://github.com/apache/logging-log4j2/pull/472
This PR adds ability to register custom resolvers for JsonTemplateLayout
This is an automated message from the Apache Git Service.
T
vy commented on pull request #472:
URL: https://github.com/apache/logging-log4j2/pull/472#issuecomment-790522511
Hey @radut! This feature is something definitely on my radar, see
[LOG4J2-3004](https://issues.apache.org/jira/browse/LOG4J2-3004). The reason we
haven't made resolver registry
vy closed pull request #472:
URL: https://github.com/apache/logging-log4j2/pull/472
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
vy merged pull request #471:
URL: https://github.com/apache/logging-log4j2/pull/471
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
radut commented on pull request #472:
URL: https://github.com/apache/logging-log4j2/pull/472#issuecomment-790543060
`JsonTemplateLayout` is a good idea, you could define specific constants
like `"@version": 1`(number) or lets say `"source" : "log4j"`(string). What I
am looking for is rewri
radut edited a comment on pull request #472:
URL: https://github.com/apache/logging-log4j2/pull/472#issuecomment-790543060
`JsonTemplateLayout` is a good idea, you could define specific constants
like `"@version": 1`(number) or lets say `"source" : "log4j"`(string). What I
am looking for i
vy commented on pull request #472:
URL: https://github.com/apache/logging-log4j2/pull/472#issuecomment-790586776
> `JsonTemplateLayout` is a good idea, you could define specific constants
like `"@version": 1`(number) or lets say `"source" : "log4j"`(string). What I
am looking for is rewrit
radut commented on pull request #472:
URL: https://github.com/apache/logging-log4j2/pull/472#issuecomment-790592929
stringified doesn't seem to be working(or at least, not as I expect it to):
log4j2.xml
```
```
```
ThreadContext.push("tcVal2", 2);
`
radut edited a comment on pull request #472:
URL: https://github.com/apache/logging-log4j2/pull/472#issuecomment-790592929
stringified doesn't seem to be working(or at least, not as I expect it to):
log4j2.xml
```
```
```json template
{
"mdc" : {
"$res
vy commented on pull request #472:
URL: https://github.com/apache/logging-log4j2/pull/472#issuecomment-791330965
So, I guess, both of us are right.
1. Yes, `JsonTemplateLayout` can serialize any object type, not only
strings. `JTL` accesses to the thread context data using
`LogEvent
vy commented on pull request #472:
URL: https://github.com/apache/logging-log4j2/pull/472#issuecomment-791402442
I think this shortcoming has already been raised in the past, see
[LOG4J2-1648](https://issues.apache.org/jira/browse/LOG4J2-1648). Apparently
such a feature would have other im
radut commented on pull request #472:
URL: https://github.com/apache/logging-log4j2/pull/472#issuecomment-792049028
@vy this `ObjectThreadContextMap` worked. Altough is there any way to still
have this in a webApp ?
I didn't tried yet in a spring boot application, but there the
`javax.s
vy commented on pull request #472:
URL: https://github.com/apache/logging-log4j2/pull/472#issuecomment-792336434
Yes, just set both of the `log4j2.is.webapp` and
`log4j2.enable.threadlocals` system properties to `true`.
This
vy edited a comment on pull request #472:
URL: https://github.com/apache/logging-log4j2/pull/472#issuecomment-792336434
Yes, just set `log4j2.is.webapp` to `false` and `log4j2.enable.threadlocals`
to `true`.
This is an autom
rm5248 merged pull request #53:
URL: https://github.com/apache/logging-log4cxx/pull/53
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
rmannibucau opened a new pull request #473:
URL: https://github.com/apache/logging-log4j2/pull/473
Giess the title is enough to understand what happens ;).
Long story short the handlesThrowable() logic to skip forced (by default)
append of the exception does not work as soon as encoding
dependabot[bot] closed pull request #464:
URL: https://github.com/apache/logging-log4j2/pull/464
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
dependabot[bot] opened a new pull request #474:
URL: https://github.com/apache/logging-log4j2/pull/474
Bumps tomcat-catalina from 8.5.20 to 10.0.4.
[ with log4cxx.
This intentionally does not utilize fmt within log4cxx, to avoid
dependencies that are
rm5248 opened a new pull request #55:
URL: https://github.com/apache/logging-log4cxx/pull/55
By turning the `LogManager::repositorySelector` into a std::shared_ptr as
part of the smart pointer conversion, it is now possible to know when the
`LogManager::repositorySelector` is valid or not
carterkozak opened a new pull request #475:
URL: https://github.com/apache/logging-log4j2/pull/475
This allows LoggerContext lookups to avoid searching for the calling
class to discover a classloader when the ContextSelector implementation
is declared to be agnostic to the class loader
carterkozak commented on a change in pull request #475:
URL: https://github.com/apache/logging-log4j2/pull/475#discussion_r595570063
##
File path:
log4j-slf4j18-impl/src/main/java/org/apache/logging/slf4j/Log4jLoggerFactory.java
##
@@ -47,8 +47,12 @@ protected Logger newLogger
ams-tschoening commented on pull request #54:
URL: https://github.com/apache/logging-log4cxx/pull/54#issuecomment-803595060
I get the following warning in Visual Studio when building everything:
```
CMake Warning at src/examples/cpp/CMakeLists.txt:15 (find_package):
By not pro
rm5248 merged pull request #55:
URL: https://github.com/apache/logging-log4cxx/pull/55
--
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.
For queries about this service, ple
rgoers commented on a change in pull request #475:
URL: https://github.com/apache/logging-log4j2/pull/475#discussion_r598352032
##
File path:
log4j-slf4j18-impl/src/main/java/org/apache/logging/slf4j/Log4jLoggerFactory.java
##
@@ -47,8 +47,12 @@ protected Logger newLogger(fina
rm5248 commented on pull request #54:
URL: https://github.com/apache/logging-log4cxx/pull/54#issuecomment-803674989
> Or should we make looking for that package simply
[silent](https://cmake.org/cmake/help/latest/command/find_package.html)?
>
> ```
> find_package(fmt QUIET)
> `
rgoers commented on a change in pull request #475:
URL: https://github.com/apache/logging-log4j2/pull/475#discussion_r598352032
##
File path:
log4j-slf4j18-impl/src/main/java/org/apache/logging/slf4j/Log4jLoggerFactory.java
##
@@ -47,8 +47,12 @@ protected Logger newLogger(fina
rm5248 merged pull request #54:
URL: https://github.com/apache/logging-log4cxx/pull/54
--
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.
For queries about this service, ple
carterkozak commented on a change in pull request #475:
URL: https://github.com/apache/logging-log4j2/pull/475#discussion_r598688410
##
File path:
log4j-slf4j18-impl/src/main/java/org/apache/logging/slf4j/Log4jLoggerFactory.java
##
@@ -47,8 +47,12 @@ protected Logger newLogger
carterkozak commented on a change in pull request #475:
URL: https://github.com/apache/logging-log4j2/pull/475#discussion_r598920010
##
File path:
log4j-slf4j18-impl/src/main/java/org/apache/logging/slf4j/Log4jLoggerFactory.java
##
@@ -47,8 +47,12 @@ protected Logger newLogger
carterkozak commented on a change in pull request #475:
URL: https://github.com/apache/logging-log4j2/pull/475#discussion_r598992139
##
File path:
log4j-core/src/main/java/org/apache/logging/log4j/core/async/BasicAsyncLoggerContextSelector.java
##
@@ -0,0 +1,85 @@
+/*
+ * Lice
carterkozak commented on pull request #455:
URL: https://github.com/apache/logging-log4j2/pull/455#issuecomment-804312697
Closing this out in favor of broader changes in #475
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub an
carterkozak closed pull request #455:
URL: https://github.com/apache/logging-log4j2/pull/455
--
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.
For queries about this servic
vy opened a new pull request #476:
URL: https://github.com/apache/logging-log4j2/pull/476
This change set aims to replace statically bound JSON template resolver
factories with plugins. Along this pursuit, following side kicks are introduced:
* Added `PluginUtil` class.
* Updated
rgoers commented on a change in pull request #475:
URL: https://github.com/apache/logging-log4j2/pull/475#discussion_r599073899
##
File path:
log4j-slf4j18-impl/src/main/java/org/apache/logging/slf4j/Log4jLoggerFactory.java
##
@@ -47,8 +47,12 @@ protected Logger newLogger(fina
rgoers commented on a change in pull request #475:
URL: https://github.com/apache/logging-log4j2/pull/475#discussion_r599073899
##
File path:
log4j-slf4j18-impl/src/main/java/org/apache/logging/slf4j/Log4jLoggerFactory.java
##
@@ -47,8 +47,12 @@ protected Logger newLogger(fina
vy commented on pull request #476:
URL: https://github.com/apache/logging-log4j2/pull/476#issuecomment-804710313
Note that this issue addresses the request in #472.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
henryw374 opened a new pull request #477:
URL: https://github.com/apache/logging-log4j2/pull/477
the underlying Map is typed so the put methods on MapMessage
can also be.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and
carterkozak opened a new pull request #478:
URL: https://github.com/apache/logging-log4j2/pull/478
--
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.
For queries about this
carterkozak commented on pull request #478:
URL: https://github.com/apache/logging-log4j2/pull/478#issuecomment-805317341
Incoming test case, will conflict with the other branch I'm working on,
however I'd prefer to merge this first and avoid duplicating bugs in the new
BasicAsyncLoggerCon
carterkozak edited a comment on pull request #478:
URL: https://github.com/apache/logging-log4j2/pull/478#issuecomment-805317341
Test case conflicts with the other branch I'm working on, however I'd prefer
to merge this first and avoid duplicating bugs in the new
BasicAsyncLoggerContextSel
carterkozak closed pull request #478:
URL: https://github.com/apache/logging-log4j2/pull/478
--
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.
For queries about this servic
carterkozak commented on pull request #478:
URL: https://github.com/apache/logging-log4j2/pull/478#issuecomment-805390676
merged
--
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 comm
carterkozak closed pull request #475:
URL: https://github.com/apache/logging-log4j2/pull/475
--
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.
For queries about this servic
carterkozak commented on pull request #475:
URL: https://github.com/apache/logging-log4j2/pull/475#issuecomment-805416177
Merged support for `isClassLoaderDependent` into release-2.x and master.
--
This is an automated message from the Apache Git Service.
To respond to the message, please
carterkozak opened a new pull request #479:
URL: https://github.com/apache/logging-log4j2/pull/479
This adds a new `BasicAsyncLoggerContextSelector` to allow fully
asynchronous logging without the overhead of classloader lookups, as well as an
improvement to walk the stack at most once rat
carterkozak commented on pull request #479:
URL: https://github.com/apache/logging-log4j2/pull/479#issuecomment-806164744
merged
--
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 comm
carterkozak closed pull request #479:
URL: https://github.com/apache/logging-log4j2/pull/479
--
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.
For queries about this servic
vy commented on pull request #477:
URL: https://github.com/apache/logging-log4j2/pull/477#issuecomment-806455867
@henryw374, I have mentioned about your PR in the dev mailing list, there is
[a discussion going
on](https://mail-archives.apache.org/mod_mbox/logging-dev/202103.mbox/%3CCAP7pH7
henryw374 commented on pull request #477:
URL: https://github.com/apache/logging-log4j2/pull/477#issuecomment-806502079
Thanks. I'll look in the forum
--
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 g
henryw374 commented on pull request #477:
URL: https://github.com/apache/logging-log4j2/pull/477#issuecomment-806511345
I've sent a subscribe message to the list now.
To add a bit more info, there is a constructor of MapMessage which takes a
single map arg :
```
pu
pgomulka commented on pull request #140:
URL: https://github.com/apache/logging-log4j2/pull/140#issuecomment-806713000
@jvz @rmannibucau any reason why this wasn't merged into release-2.x?
at the moment in 2.x `LoaderUtil#getClassloaders` does not take into account
security manager and
rmannibucau commented on pull request #140:
URL: https://github.com/apache/logging-log4j2/pull/140#issuecomment-806718786
@pgomulka no reason, a lot of master should get released soon (like SPI
improvements, this, probably https://github.com/apache/logging-log4j2/pull/473
too and so on) so
rm5248 opened a new pull request #56:
URL: https://github.com/apache/logging-log4cxx/pull/56
--
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.
For queries about this servic
rm5248 opened a new pull request #57:
URL: https://github.com/apache/logging-log4cxx/pull/57
--
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.
For queries about this servic
rm5248 merged pull request #56:
URL: https://github.com/apache/logging-log4cxx/pull/56
--
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.
For queries about this service, ple
rm5248 merged pull request #57:
URL: https://github.com/apache/logging-log4cxx/pull/57
--
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.
For queries about this service, ple
rm5248 opened a new pull request #58:
URL: https://github.com/apache/logging-log4cxx/pull/58
Add some new options to check for ABI changes between an old, known version
of the ABI and the newest build version of the ABI.
--
This is an automated message from the Apache Git Service.
To res
rgoers opened a new pull request #480:
URL: https://github.com/apache/logging-log4j2/pull/480
Moves master to Java11.
1. Removes all -java9 modules.
2. Required version upgrades to lots of stuff.
3. Log4j-api and Log4j-plugins are true JPMS modules. Not much else is yet.
Getti
carterkozak commented on a change in pull request #480:
URL: https://github.com/apache/logging-log4j2/pull/480#discussion_r603666062
##
File path:
log4j-api/src/main/java/org/apache/logging/log4j/util/StackLocator.java
##
@@ -16,75 +16,23 @@
*/
package org.apache.logging.lo
carterkozak commented on a change in pull request #480:
URL: https://github.com/apache/logging-log4j2/pull/480#discussion_r603671718
##
File path:
log4j-core/src/main/java/org/apache/logging/log4j/core/time/internal/SystemClock.java
##
@@ -16,13 +16,19 @@
*/
package org.apa
rm5248 opened a new pull request #59:
URL: https://github.com/apache/logging-log4cxx/pull/59
Link with ODBC library if found on OSX and Linux.
--
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
rgoers commented on a change in pull request #480:
URL: https://github.com/apache/logging-log4j2/pull/480#discussion_r603718254
##
File path:
log4j-core/src/main/java/org/apache/logging/log4j/core/time/internal/SystemClock.java
##
@@ -16,13 +16,19 @@
*/
package org.apache.l
rgoers commented on a change in pull request #480:
URL: https://github.com/apache/logging-log4j2/pull/480#discussion_r603718254
##
File path:
log4j-core/src/main/java/org/apache/logging/log4j/core/time/internal/SystemClock.java
##
@@ -16,13 +16,19 @@
*/
package org.apache.l
rgoers commented on a change in pull request #480:
URL: https://github.com/apache/logging-log4j2/pull/480#discussion_r603790813
##
File path:
log4j-api/src/main/java/org/apache/logging/log4j/util/StackLocator.java
##
@@ -16,75 +16,23 @@
*/
package org.apache.logging.log4j.u
ams-tschoening commented on a change in pull request #59:
URL: https://github.com/apache/logging-log4cxx/pull/59#discussion_r603874214
##
File path: src/main/include/CMakeLists.txt
##
@@ -67,12 +67,17 @@ include(CheckCXXSymbolExists)
include(CheckIncludeFiles)
include(CheckIn
rm5248 commented on pull request #59:
URL: https://github.com/apache/logging-log4cxx/pull/59#issuecomment-810618371
Dang... not sure how those spaces keep creeping in. I'll look into making a
pre-commit hook to check for those, it should help reduce those errors. Should
be fixed now thou
ams-tschoening commented on pull request #59:
URL: https://github.com/apache/logging-log4cxx/pull/59#issuecomment-810923318
> Dang... not sure how those spaces keep creeping in.[...]
`.editorconfig` is the root cause most likely, that contains spaces for
shell scripts and `CMakeLists
rm5248 merged pull request #59:
URL: https://github.com/apache/logging-log4cxx/pull/59
--
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.
For queries about this service, ple
perry2of5 commented on pull request #480:
URL: https://github.com/apache/logging-log4j2/pull/480#issuecomment-812102267
Building on windows, Zulu Java 11, Maven 3.6.3, I see this warning in
log4j-api, log4j-plugins, and others:
[WARNING] * Required filename-based automodules detected:
[
rgoers commented on pull request #480:
URL: https://github.com/apache/logging-log4j2/pull/480#issuecomment-812125020
@perry2of5 Thanks. That is likely related to why I couldn't get the
log4j-osgi to run its tests. I'll have to figure out what that warning means
and fix it.
--
This is an
rgoers edited a comment on pull request #480:
URL: https://github.com/apache/logging-log4j2/pull/480#issuecomment-812125020
@perry2of5 Thanks. That is likely related to why I couldn't get the
log4j-osgi module to run its tests. I'll have to figure out what that warning
means and fix it.
rm5248 opened a new pull request #60:
URL: https://github.com/apache/logging-log4cxx/pull/60
Every time a LoggingEvent is created, part of the information that is stored
in the LoggingEvent is the name of the thread that the log is from. By turning
this into a `thread_local` variable and
Noobgam opened a new pull request #481:
URL: https://github.com/apache/logging-log4j2/pull/481
When configured incorrectly, the ErrorHandler::error method will be called
very often. As an example of such behavior, you can try stopping the appender
manually.
This will result in `Erro
carterkozak commented on pull request #481:
URL: https://github.com/apache/logging-log4j2/pull/481#issuecomment-812636274
Thank you for reporting, great find! Would you mind filing jira issue for
tracking [here](https://issues.apache.org/jira/browse/LOG4J2)?
--
This is an automated messa
Noobgam commented on pull request #481:
URL: https://github.com/apache/logging-log4j2/pull/481#issuecomment-812639094
Sure https://issues.apache.org/jira/browse/LOG4J2-3060
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and
rgoers merged pull request #480:
URL: https://github.com/apache/logging-log4j2/pull/480
--
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.
For queries about this service, pl
vy merged pull request #476:
URL: https://github.com/apache/logging-log4j2/pull/476
--
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.
For queries about this service, please
dependabot[bot] commented on pull request #414:
URL: https://github.com/apache/logging-log4j2/pull/414#issuecomment-813110469
Superseded by #482.
--
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
dependabot[bot] opened a new pull request #482:
URL: https://github.com/apache/logging-log4j2/pull/482
Bumps [maven-core](https://github.com/apache/maven) from 3.6.0 to 3.8.1.
Commits
https://github.com/apache/maven/commit/05c21c65bdfed0f71a2f2ada8b84da59348c4c5d";>05c21c6
[ma
dependabot[bot] closed pull request #414:
URL: https://github.com/apache/logging-log4j2/pull/414
--
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.
For queries about this se
rm5248 commented on pull request #60:
URL: https://github.com/apache/logging-log4cxx/pull/60#issuecomment-814452988
That is actually a much simpler implementation. I didn't think about doing
it that way, as I was thinking about having a fallback method of having a map
of thread<->name. T
dependabot[bot] commented on pull request #474:
URL: https://github.com/apache/logging-log4j2/pull/474#issuecomment-814555147
Superseded by #483.
--
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
1101 - 1200 of 7264 matches
Mail list logo
