ams-tschoening closed pull request #18: Conditionally exclude tests that
require the external 'zip' or 'gzip'
URL: https://github.com/apache/logging-log4cxx/pull/18
This is an automated message from the Apache Git Service.
T
rgoers commented on issue #158: [LOG4J2-2280] Introduce an Apache Pulsar log4j
appender
URL: https://github.com/apache/logging-log4j2/pull/158#issuecomment-588032446
Is this really needed given that Apache Pulsar is already distributing a
Pulsar Appender?
https://github.com/apache/pulsar/
cyrixsimon commented on issue #307: [LOG4J2-2652] JSON output wrong when using
additonal fields
URL: https://github.com/apache/logging-log4j2/pull/307#issuecomment-588144812
Are there any plans to make a release 2.13.1 in the next time? I need this
fix really soon in an official release, b
sebastianvoss commented on issue #3: add support for scala 2.13.0 [LOG4J2-2668]
URL: https://github.com/apache/logging-log4j-scala/pull/3#issuecomment-588274494
@jvz Thanks a lot for creating a release. Are you also able to push to Maven
Central?
---
rgoers commented on issue #307: [LOG4J2-2652] JSON output wrong when using
additonal fields
URL: https://github.com/apache/logging-log4j2/pull/307#issuecomment-588283058
My hope is to be able to do a release this weekend, but I still have a few
more issues that need to be resolved.
--
jvz commented on issue #3: add support for scala 2.13.0 [LOG4J2-2668]
URL: https://github.com/apache/logging-log4j-scala/pull/3#issuecomment-588285505
We have a release candidate in process. Due to some glitches in that release
(it's the first one being done using sbt), it seems like I'll n
willdieh commented on issue #308: LOG4J2-1192 (support dynamic Subject)
URL: https://github.com/apache/logging-log4j2/pull/308#issuecomment-588544936
Yeah, sorry, I'm not even sure what kind of unit test this would need. Go
ahead and close it if you need to, I've already implemented it in m
vy commented on issue #335: Import of LogstashLayout as JsonTemplateLayout
URL: https://github.com/apache/logging-log4j2/pull/335#issuecomment-588828193
@remkop, in case you are interested in, dae3be0 introduces the abstraction
for different caching strategies we have discussed: dummy, thre
vy commented on issue #335: Import of LogstashLayout as JsonTemplateLayout
URL: https://github.com/apache/logging-log4j2/pull/335#issuecomment-588828904
For the records, I am done. The only missing bit is getting test-jar working
for log4j-perf module.
-
rgoers commented on issue #335: Import of LogstashLayout as JsonTemplateLayout
URL: https://github.com/apache/logging-log4j2/pull/335#issuecomment-589094499
OK. I hope I can look at that this weekend. I am also planning on trying to
get a release out this weekend so I would expect to merge
MariusVolkhart opened a new pull request #340: (doc) Fix "construct" typo
URL: https://github.com/apache/logging-log4j2/pull/340
This is an automated message from the Apache Git Service.
To respond to the message, please log
MariusVolkhart opened a new pull request #341: ThreadContext: Convert static
fields to ivars
URL: https://github.com/apache/logging-log4j2/pull/341
These don't get used outside the scope of init().
This is an automated messag
MariusVolkhart opened a new pull request #342: (doc) Add info about configuring
ThreadContext via system properties
URL: https://github.com/apache/logging-log4j2/pull/342
This is an automated message from the Apache Git Serv
MariusVolkhart opened a new pull request #343: Conditionally perform status
logging calculations in PluginRegistry
URL: https://github.com/apache/logging-log4j2/pull/343
Debug status logging is typically disabled, but formatting calculations were
performed regardless.
Moving the for
carterkozak commented on a change in pull request #343: Conditionally perform
status logging calculations in PluginRegistry
URL: https://github.com/apache/logging-log4j2/pull/343#discussion_r383015802
##
File path:
log4j-plugins/src/main/java/org/apache/logging/log4j/plugins/util/P
rgoers merged pull request #340: (doc) Fix "construct" typo
URL: https://github.com/apache/logging-log4j2/pull/340
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub a
rgoers merged pull request #341: ThreadContext: Convert static fields to ivars
URL: https://github.com/apache/logging-log4j2/pull/341
This is an automated message from the Apache Git Service.
To respond to the message, please
rgoers merged pull request #342: (doc) Add info about configuring ThreadContext
via system properties
URL: https://github.com/apache/logging-log4j2/pull/342
This is an automated message from the Apache Git Service.
To respon
rgoers commented on a change in pull request #343: Conditionally perform status
logging calculations in PluginRegistry
URL: https://github.com/apache/logging-log4j2/pull/343#discussion_r383025858
##
File path:
log4j-plugins/src/main/java/org/apache/logging/log4j/plugins/util/Plugin
rgoers closed pull request #343: Conditionally perform status logging
calculations in PluginRegistry
URL: https://github.com/apache/logging-log4j2/pull/343
This is an automated message from the Apache Git Service.
To respond
rgoers commented on issue #343: Conditionally perform status logging
calculations in PluginRegistry
URL: https://github.com/apache/logging-log4j2/pull/343#issuecomment-590100716
I have applied a version of this that uses lambdas. Thanks for the good work!
--
MariusVolkhart opened a new pull request #344: LOG4J2-2790 Conditionally
allocate PluginEntry during PluginCache load
URL: https://github.com/apache/logging-log4j2/pull/344
When populating the PluginCache from resources, only allocate a new
PluginEntry if there is not already an existing o
wlfshmn opened a new pull request #345: LOG4J2-2791 - Correct JsonLayout
timestamp sorting issue
URL: https://github.com/apache/logging-log4j2/pull/345
This is an automated message from the Apache Git Service.
To respond to
wlfshmn commented on issue #345: LOG4J2-2791 - Correct JsonLayout timestamp
sorting issue
URL: https://github.com/apache/logging-log4j2/pull/345#issuecomment-591499581
Travis build issue appears to be general, and not specific to this pull
request.
flyhope opened a new pull request #26: compatible php7.2
URL: https://github.com/apache/logging-log4php/pull/26
The `each` function has been DEPRECATED as of PHP 7.2.0. Replce by `foreach`
This is an automated message from th
wlfshmn opened a new pull request #346: LOG4J2-2794 - Make unit test more
resilient to environment differences.
URL: https://github.com/apache/logging-log4j2/pull/346
This is an automated message from the Apache Git Service.
stephen-webb opened a new pull request #19: Fix support for
find_package(log4cxx) in consuming CMake projects
URL: https://github.com/apache/logging-log4cxx/pull/19
Install a using a standard CMake file name that is found by find_package()
--
shatakshidixit1 opened a new pull request #347: Updated file with Spring Boot
logging Using log4j 2 Guide
URL: https://github.com/apache/logging-log4j2/pull/347
I have written article on Spring Boot logging Using log4j 2 Guide with
complete Example.
---
prasad-acit opened a new pull request #348: LOG4J2-2793 - Unable to parse the
log LEVEL when it ends with SPACE.
URL: https://github.com/apache/logging-log4j2/pull/348
Handled leading & trailing spaces in log LEVEL.
This is a
stephen-webb opened a new pull request #20: Windows build static library support
URL: https://github.com/apache/logging-log4cxx/pull/20
This is an automated message from the Apache Git Service.
To respond to the message, plea
ams-tschoening commented on issue #20: Windows build static library support
URL: https://github.com/apache/logging-log4cxx/pull/20#issuecomment-596384144
If I reviewed correctly, there are multiple issues with this PR:
1. it seems to reintroduce excluding tests, which I already remove
ams-tschoening removed a comment on issue #20: Windows build static library
support
URL: https://github.com/apache/logging-log4cxx/pull/20#issuecomment-596384144
If I reviewed correctly, there are multiple issues with this PR:
1. it seems to reintroduce excluding tests, which I alrea
stephen-webb commented on issue #20: Windows build static library support
URL: https://github.com/apache/logging-log4cxx/pull/20#issuecomment-596446458
The PR may have picked up some other commits. I will look at it tomorrow.
On Mon, Mar 9, 2020 at 7:04 PM Thorsten Schöning
wr
stephen-webb opened a new pull request #21: Add support for building log4cxx as
a statically linked library on Windows
URL: https://github.com/apache/logging-log4cxx/pull/21
Replacement for PR #20
This is an automated message
ams-tschoening closed pull request #20: Windows build static library support
URL: https://github.com/apache/logging-log4cxx/pull/20
This is an automated message from the Apache Git Service.
To respond to the message, please l
ams-tschoening commented on issue #20: Windows build static library support
URL: https://github.com/apache/logging-log4cxx/pull/20#issuecomment-596961591
Closing in favour of #21.
This is an automated message from the Apache G
ams-tschoening merged pull request #19: Fix support for find_package(log4cxx)
in consuming CMake projects
URL: https://github.com/apache/logging-log4cxx/pull/19
This is an automated message from the Apache Git Service.
To re
trejkaz opened a new pull request #349: Fix erroneous usage of default locale
URL: https://github.com/apache/logging-log4j2/pull/349
This is an automated message from the Apache Git Service.
To respond to the message, please
remkop commented on issue #349: Fix erroneous usage of default locale
URL: https://github.com/apache/logging-log4j2/pull/349#issuecomment-599203151
Could you add a breaking test that passes with your patch?
This is an automate
trejkaz commented on issue #349: Fix erroneous usage of default locale
URL: https://github.com/apache/logging-log4j2/pull/349#issuecomment-599222520
That seems challenging.
This is an automated message from the Apache Git Serv
trejkaz opened a new pull request #350: Introduce Policeman's Forbidden API
Checker
URL: https://github.com/apache/logging-log4j2/pull/350
This should be interesting.
This is an automated message from the Apache Git Service.
trejkaz commented on issue #349: Fix erroneous usage of default locale
URL: https://github.com/apache/logging-log4j2/pull/349#issuecomment-599265206
I thought I'd try introducing forbidden-apis, but while looking at the logs,
I notice that error-prone is in use already, so it's quite possib
remkop commented on issue #349: Fix erroneous usage of default locale
URL: https://github.com/apache/logging-log4j2/pull/349#issuecomment-599266708
If providing a test is challenging, can you at least provide a rationale on
why the change is necessary? Why is Locale.ROOT better than
Locale
trejkaz commented on issue #349: Fix erroneous usage of default locale
URL: https://github.com/apache/logging-log4j2/pull/349#issuecomment-599266980
A config file should be assumed to work the same irrespective of the locale
the machine is running in. By parsing numbers in the default local
remkop commented on issue #349: Fix erroneous usage of default locale
URL: https://github.com/apache/logging-log4j2/pull/349#issuecomment-599269469
That makes sense. Thank you for the clarification.
(Perhaps in that case a test could be created with `Locale.setDefault` where
the old
trejkaz closed pull request #350: Introduce Policeman's Forbidden API Checker
URL: https://github.com/apache/logging-log4j2/pull/350
This is an automated message from the Apache Git Service.
To respond to the message, please
trejkaz commented on issue #349: Fix erroneous usage of default locale
URL: https://github.com/apache/logging-log4j2/pull/349#issuecomment-599873519
Alright, so as it turns out, all current locales show no failure with
passing in the digits in Latin even if that locale in question uses diff
remkop commented on issue #349: Fix erroneous usage of default locale
URL: https://github.com/apache/logging-log4j2/pull/349#issuecomment-599878124
I see. I was thinking along the lines of parsing `1,000` (1000 in US locale)
vs `1.000` (1000 in French/German/Dutch locale), but if that doesn
trejkaz commented on issue #349: Fix erroneous usage of default locale
URL: https://github.com/apache/logging-log4j2/pull/349#issuecomment-599881590
Ah, you're right, that case does break it because it turns into a decimal
point.
remkop commented on issue #349: Fix erroneous usage of default locale
URL: https://github.com/apache/logging-log4j2/pull/349#issuecomment-599919068
Thanks for adding the test. This looks good to merge.
This is an automated me
akeeton opened a new pull request #57: (doc) Fix link to FileAppender Class docs
URL: https://github.com/apache/logging-log4net/pull/57
This is an automated message from the Apache Git Service.
To respond to the message, plea
kevinleturc opened a new pull request #351: LOG4J2-1360 - Provide a Log4j
implementation of System.Logger
URL: https://github.com/apache/logging-log4j2/pull/351
You can find below a POC of JEP 264 implementation with log4j. I may have
missed some implementation details, let me know if ther
rgoers commented on a change in pull request #351: LOG4J2-1360 - Provide a
Log4j implementation of System.Logger
URL: https://github.com/apache/logging-log4j2/pull/351#discussion_r395966722
##
File path: log4j-jpl/pom.xml
##
@@ -0,0 +1,255 @@
+
+
+
+http://maven.apache.org
Kuojian21 opened a new pull request #352: fix bug:support includeLocation for
AsyncLogger
URL: https://github.com/apache/logging-log4j2/pull/352
This bug cause that the "%L" is invalid for AsyncLogger.
This is an automated me
Kuojian21 opened a new pull request #352: fix bug:support includeLocation for
AsyncLogger
URL: https://github.com/apache/logging-log4j2/pull/352
This bug cause that the "%L" is invalid for AsyncLogger.
This is an automated me
Kuojian21 closed pull request #352: fix bug:support includeLocation for
AsyncLogger
URL: https://github.com/apache/logging-log4j2/pull/352
This is an automated message from the Apache Git Service.
To respond to the message,
kevinleturc commented on a change in pull request #351: LOG4J2-1360 - Provide a
Log4j implementation of System.Logger
URL: https://github.com/apache/logging-log4j2/pull/351#discussion_r396075408
##
File path: log4j-jpl/pom.xml
##
@@ -0,0 +1,255 @@
+
+
+
+http://maven.apach
kevinleturc commented on issue #351: LOG4J2-1360 - Provide a Log4j
implementation of System.Logger
URL: https://github.com/apache/logging-log4j2/pull/351#issuecomment-602175494
I added the site section with the right maven plugins to make the build
succeed.
In this addition, I faced
dumitrubogdanmihai opened a new pull request #353: Fix initialization when
security is enabled
URL: https://github.com/apache/logging-log4j2/pull/353
File:exists may cause an AccessControlException in case of an strict
SecurityManager.
This would fail the initialization.
--
Shazwazza commented on issue #40: This fixes the Mutex name in the
RollingFileAppender
URL: https://github.com/apache/logging-log4net/pull/40#issuecomment-602919518
Any updates on this?
This is an automated message from the A
rgoers commented on issue #40: This fixes the Mutex name in the
RollingFileAppender
URL: https://github.com/apache/logging-log4net/pull/40#issuecomment-602928103
Please see the latest emails on the logging developer's list.
T
javieraviles opened a new pull request #354: DOCUMENTATION change. Adding
target to Console appender in YAML config
URL: https://github.com/apache/logging-log4j2/pull/354
Console appender requires target property in order to work for YAML
configuration
uschindler opened a new pull request #355: LOG4J2-2761: Fix
FileUtils#fileFromUri to works correctly with Securi…
URL: https://github.com/apache/logging-log4j2/pull/355
…tyManager and also fix URI parsing to behave sane with standards
---
Kuojian21 closed pull request #352: fix bug:support includeLocation for
AsyncLogger
URL: https://github.com/apache/logging-log4j2/pull/352
This is an automated message from the Apache Git Service.
To respond to the message,
Kuojian21 opened a new pull request #352: fix bug:support includeLocation for
AsyncLogger
URL: https://github.com/apache/logging-log4j2/pull/352
This bug cause that the "%L" is invalid for AsyncLogger.
This is an automated me
uschindler commented on issue #355: LOG4J2-2761: Fix FileUtils#fileFromUri to
works correctly with Securi…
URL: https://github.com/apache/logging-log4j2/pull/355#issuecomment-604301231
This did not happen locally:
```
[ERROR] Failures:
[ERROR] FileOutputTest.testConfig:46 St
uschindler commented on issue #355: LOG4J2-2761: Fix FileUtils#fileFromUri to
works correctly with Securi…
URL: https://github.com/apache/logging-log4j2/pull/355#issuecomment-604324659
I figured out where the issue is: If the file does not exist,
`fileFromUri(URI)` returns null. The previo
uschindler edited a comment on issue #355: LOG4J2-2761: Fix
FileUtils#fileFromUri to works correctly with Securi…
URL: https://github.com/apache/logging-log4j2/pull/355#issuecomment-604324659
I figured out where the issue is: If the file does not exist,
`fileFromUri(URI)` returns null. The
rmannibucau opened a new pull request #356: [LOG4J2-2809] avoid NPE because the
stacklocator returned null
URL: https://github.com/apache/logging-log4j2/pull/356
This is an automated message from the Apache Git Service.
To r
rgoers merged pull request #356: [LOG4J2-2809] avoid NPE because the
stacklocator returned null
URL: https://github.com/apache/logging-log4j2/pull/356
This is an automated message from the Apache Git Service.
To respond to t
rgoers merged pull request #355: LOG4J2-2761: Fix FileUtils#fileFromUri to
works correctly with Securi…
URL: https://github.com/apache/logging-log4j2/pull/355
This is an automated message from the Apache Git Service.
To resp
rgoers merged pull request #354: DOCUMENTATION fix. Adding target to Console
appender in YAML config
URL: https://github.com/apache/logging-log4j2/pull/354
This is an automated message from the Apache Git Service.
To respond
rgoers commented on issue #353: Fix initialization when security is enabled
URL: https://github.com/apache/logging-log4j2/pull/353#issuecomment-605512714
Fixed by PR #355
This is an automated message from the Apache Git Servi
rgoers closed pull request #353: Fix initialization when security is enabled
URL: https://github.com/apache/logging-log4j2/pull/353
This is an automated message from the Apache Git Service.
To respond to the message, please l
rgoers merged pull request #352: fix bug:support includeLocation for AsyncLogger
URL: https://github.com/apache/logging-log4j2/pull/352
This is an automated message from the Apache Git Service.
To respond to the message, plea
rgoers merged pull request #344: LOG4J2-2790 Conditionally allocate PluginEntry
during PluginCache load
URL: https://github.com/apache/logging-log4j2/pull/344
This is an automated message from the Apache Git Service.
To resp
rgoers closed pull request #347: Updated file with Spring Boot logging Using
log4j 2 Guide
URL: https://github.com/apache/logging-log4j2/pull/347
This is an automated message from the Apache Git Service.
To respond to the me
rgoers commented on a change in pull request #347: Updated file with Spring
Boot logging Using log4j 2 Guide
URL: https://github.com/apache/logging-log4j2/pull/347#discussion_r388984154
##
File path: src/site/markdown/articles.md
##
@@ -43,6 +43,8 @@ guide for up-to-date a
rgoers commented on issue #351: LOG4J2-1360 - Provide a Log4j implementation of
System.Logger
URL: https://github.com/apache/logging-log4j2/pull/351#issuecomment-605791148
I am having a difficult time getting the site build to work with this. When
I use Java 11 it fails in the JMX GUI modu
rgoers edited a comment on issue #351: LOG4J2-1360 - Provide a Log4j
implementation of System.Logger
URL: https://github.com/apache/logging-log4j2/pull/351#issuecomment-605791148
I am having a difficult time getting the site build to work with this. When
I use Java 11 it fails in the JMX G
ams-tschoening commented on a change in pull request #21: Add support for
building log4cxx as a statically linked library on Windows
URL: https://github.com/apache/logging-log4cxx/pull/21#discussion_r390155388
##
File path: src/site/apt/building/cmake.apt
##
@@ -50,6 +50,1
ams-tschoening commented on issue #21: Add support for building log4cxx as a
statically linked library on Windows
URL: https://github.com/apache/logging-log4cxx/pull/21#issuecomment-605838327
Any reason why `-DAPU_STATIC` and `-DAPR_STATIC` are not documented with
something like `=off|on`
stephen-webb commented on issue #21: Add support for building log4cxx as a
statically linked library on Windows
URL: https://github.com/apache/logging-log4cxx/pull/21#issuecomment-605849220
No, they work the same, except the Build shared is on by default. The =on
does no more than the ex
stephen-webb commented on issue #21: Add support for building log4cxx as a
statically linked library on Windows
URL: https://github.com/apache/logging-log4cxx/pull/21#issuecomment-605873078
Correction, =yes is equivalent to existence of a definition
On Mon, Mar 30, 2020, 7:10 PM Step
ams-tschoening commented on issue #21: Add support for building log4cxx as a
statically linked library on Windows
URL: https://github.com/apache/logging-log4cxx/pull/21#issuecomment-605877990
Then please add `=yes|no|on|off` as necessary/useful for `-D*_STATIC`, so
that its in line with th
ams-tschoening merged pull request #21: Add support for building log4cxx as a
statically linked library on Windows
URL: https://github.com/apache/logging-log4cxx/pull/21
This is an automated message from the Apache Git Servi
ss5611 commented on issue #57: (doc) Fix link to FileAppender Class docs
URL: https://github.com/apache/logging-log4net/pull/57#issuecomment-606492235
When I publish my project, It said :
[library] -> log4net 2.0.8 -> System.Net.Sockets 4.1.0 ->
runtime.win.System.Net.Sockets 4.3.0 -> Sy
abuechler opened a new pull request #552:
URL: https://github.com/apache/logging-log4j2/pull/552
--
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: n
abuechler commented on pull request #552:
URL: https://github.com/apache/logging-log4j2/pull/552#issuecomment-43107
https://github.com/apache/logging-log4j2/blob/master/log4j-core/src/main/resources/Log4j-config.xsd#L190
--
This is an automated message from the Apache Git Service.
To
abuechler commented on pull request #552:
URL: https://github.com/apache/logging-log4j2/pull/552#issuecomment-889113157
Build fails, because master is failing since 9th of July 2021 😞
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to
garydgregory commented on pull request #552:
URL: https://github.com/apache/logging-log4j2/pull/552#issuecomment-889115293
@abuechler
Please rebase on master.
TY
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use
abuechler commented on pull request #552:
URL: https://github.com/apache/logging-log4j2/pull/552#issuecomment-889120320
@garydgregory
I already
[did](https://github.com/abuechler/logging-log4j2/commits/3f8822df8f2baf4a38cdd6bc27f9498deb1abe3b).
--
This is an automated message fro
abuechler edited a comment on pull request #552:
URL: https://github.com/apache/logging-log4j2/pull/552#issuecomment-889120320
@garydgregory
I already
[did](https://github.com/abuechler/logging-log4j2/commits/3f8822df8f2baf4a38cdd6bc27f9498deb1abe3b).
But since master is still fail
radut commented on pull request #476:
URL: https://github.com/apache/logging-log4j2/pull/476#issuecomment-891031824
Do you have any example how we can write custom resolvers for this plugin ?
--
This is an automated message from the Apache Git Service.
To respond to the message, please lo
radut edited a comment on pull request #476:
URL: https://github.com/apache/logging-log4j2/pull/476#issuecomment-891031824
Do you have any example how we can write(and register) custom resolvers for
this plugin ?
--
This is an automated message from the Apache Git Service.
To respond to
vy commented on pull request #476:
URL: https://github.com/apache/logging-log4j2/pull/476#issuecomment-891529244
@radut, we have [a whole
section](/apache/logging-log4j2/blob/release-2.x/src/site/asciidoc/manual/json-template-layout.adoc.vm#L1529)
dedicated to this, yet 2.15.0 is not relea
radut commented on pull request #476:
URL: https://github.com/apache/logging-log4j2/pull/476#issuecomment-891568440
I was hoping that I could test in master branch until the release of 2.15.0,
maybe small adjustments could be made until release... I would like to override
`MarkerResolver`
vy commented on pull request #476:
URL: https://github.com/apache/logging-log4j2/pull/476#issuecomment-891572446
Is working with `2.15.0-SNAPSHOT` (which is available in Maven Central) an
option for you?
--
This is an automated message from the Apache Git Service.
To respond to the messa
radut commented on pull request #476:
URL: https://github.com/apache/logging-log4j2/pull/476#issuecomment-891580440
cannot find the file here :
https://repo1.maven.org/maven2/org/apache/logging/log4j/log4j-core/2.15.0-SNAPSHOT/log4j-core-2.15.0-SNAPSHOT.jar
--
This is an automated mess
sman-81 commented on pull request #548:
URL: https://github.com/apache/logging-log4j2/pull/548#issuecomment-891590238
How will you proceed with my PR?
--
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
2701 - 2800 of 7264 matches
Mail list logo