dependabot[bot] opened a new pull request #718:
URL: https://github.com/apache/logging-log4j2/pull/718
Bumps
[elasticsearch-rest-high-level-client](https://github.com/elastic/elasticsearch)
from 7.6.2 to 7.16.3.
Release notes
Sourced from https://github.com/elastic/elasticsearch/
swebb2066 edited a comment on pull request #105:
URL: https://github.com/apache/logging-log4cxx/pull/105#issuecomment-1015034924
If `static` objects are being destroyed while another thread is logging,
then `APRInitializer` is also destroyed (which is bad). So all logging activity
must be
swebb2066 edited a comment on pull request #105:
URL: https://github.com/apache/logging-log4cxx/pull/105#issuecomment-1015034924
If `static` objects are being destroyed while another thread is logging,
then `APRInitializer` is also destroyed (which is bad). So all logging activity
must be
swebb2066 commented on pull request #105:
URL: https://github.com/apache/logging-log4cxx/pull/105#issuecomment-1015034924
If `static` objects are being destroyed while another thread is logging,
then `APRInitializer` is also destroyed (which is bad). So all logging activity
must be stopped
[
https://issues.apache.org/jira/browse/LOG4J2-3345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carter Kozak closed LOG4J2-3345.
> log4j-jpl must handle parameters as MessageFormat args
> ---
[
https://issues.apache.org/jira/browse/LOG4J2-3345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carter Kozak updated LOG4J2-3345:
-
Fix Version/s: 2.17.2
> log4j-jpl must handle parameters as MessageFormat args
> ---
[
https://issues.apache.org/jira/browse/LOG4J2-3345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carter Kozak resolved LOG4J2-3345.
--
Resolution: Fixed
> log4j-jpl must handle parameters as MessageFormat args
> -
[
https://issues.apache.org/jira/browse/LOG4J2-3345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17477512#comment-17477512
]
ASF subversion and git services commented on LOG4J2-3345:
-
Commi
[
https://issues.apache.org/jira/browse/LOG4J2-3345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17477510#comment-17477510
]
ASF subversion and git services commented on LOG4J2-3345:
-
Commi
carterkozak merged pull request #712:
URL: https://github.com/apache/logging-log4j2/pull/712
--
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: notif
carterkozak merged pull request #713:
URL: https://github.com/apache/logging-log4j2/pull/713
--
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: notif
[
https://issues.apache.org/jira/browse/LOG4J2-1792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17477503#comment-17477503
]
Gary D. Gregory commented on LOG4J2-1792:
-
Right, this was fixed under a differe
carterkozak commented on pull request #717:
URL: https://github.com/apache/logging-log4j2/pull/717#issuecomment-1014986859
@rgoers I can't seem to find the performance test you added as
`log4j-core/src/test/java/org/apache/logging/log4j/core/LoggingTest.java`
In the original issue, initi
swebb2066 merged pull request #104:
URL: https://github.com/apache/logging-log4cxx/pull/104
--
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: notifi
swebb2066 merged pull request #103:
URL: https://github.com/apache/logging-log4cxx/pull/103
--
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: notifi
[
https://issues.apache.org/jira/browse/LOG4J2-2930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17477501#comment-17477501
]
Ralph Goers commented on LOG4J2-2930:
-
Note that for encrypting logs I would imagine
BUILD UNSTABLE
Build URL
https://ci-builds.apache.org/job/Logging/job/log4j/job/release-2.x/759/
Project:
release-2.x
Date of build:
Mon, 17 Jan 2022 23:32:33 +
Build duration:
1 hr 7 min and counting
JUnit Tests
Name: (root) Failed: 0 test(s), P
[
https://issues.apache.org/jira/browse/LOG4J2-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17477480#comment-17477480
]
Matt Sicker commented on LOG4J2-1870:
-
That's meant as "use the async option in the
[
https://issues.apache.org/jira/browse/LOG4J2-3322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Sicker resolved LOG4J2-3322.
-
Resolution: Duplicate
Definitely a duplicate.
> Provide StackTraceElements in Log4-Scala macros
[
https://issues.apache.org/jira/browse/LOG4J2-3322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17477477#comment-17477477
]
Matt Sicker commented on LOG4J2-3322:
-
Possible duplicate of LOG4J2-1449.
> Provide
[
https://issues.apache.org/jira/browse/LOG4J2-1629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17477475#comment-17477475
]
Matt Sicker commented on LOG4J2-1629:
-
This can be more easily supported with the Ja
carterkozak opened a new pull request #717:
URL: https://github.com/apache/logging-log4j2/pull/717
draft, I need to validate performance related to the original reason this
ran on another thread: https://issues.apache.org/jira/browse/LOG4J2-2867
Now that the serviceloader is guarded
[
https://issues.apache.org/jira/browse/LOG4J2-1792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17477473#comment-17477473
]
Ralph Goers commented on LOG4J2-1792:
-
I think Gary is working on fixing this. It se
[
https://issues.apache.org/jira/browse/LOG4J2-3344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17477474#comment-17477474
]
Matt Sicker commented on LOG4J2-3344:
-
If we were to support more complex map data t
[
https://issues.apache.org/jira/browse/LOG4J2-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17477472#comment-17477472
]
Ralph Goers commented on LOG4J2-1870:
-
How is one supposed to include the Kafka Appe
[
https://issues.apache.org/jira/browse/LOG4J2-2930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17477470#comment-17477470
]
Matt Sicker commented on LOG4J2-2930:
-
Possibly related to LOG4J2-1000.
> Add plugi
[
https://issues.apache.org/jira/browse/LOG4J2-3343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17477468#comment-17477468
]
Matt Sicker commented on LOG4J2-3343:
-
It looks better once you have more complex pa
vy merged pull request #716:
URL: https://github.com/apache/logging-log4j2/pull/716
--
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 merged pull request #715:
URL: https://github.com/apache/logging-log4j2/pull/715
--
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-
[
https://issues.apache.org/jira/browse/LOG4J2-2862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17477463#comment-17477463
]
Volkan Yazici commented on LOG4J2-2862:
---
You can introduce this masking feature to
[
https://issues.apache.org/jira/browse/LOG4J2-2862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Volkan Yazici reassigned LOG4J2-2862:
-
Assignee: Volkan Yazici
> Add Masking to JsonTemplateLayout
> -
[
https://issues.apache.org/jira/browse/LOG4J2-2862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Volkan Yazici resolved LOG4J2-2862.
---
Resolution: Information Provided
> Add Masking to JsonTemplateLayout
> -
[
https://issues.apache.org/jira/browse/LOG4J2-2862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17477463#comment-17477463
]
Volkan Yazici edited comment on LOG4J2-2862 at 1/17/22, 10:29 PM:
[
https://issues.apache.org/jira/browse/LOG4J2-3343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17477462#comment-17477462
]
Volkan Yazici commented on LOG4J2-3343:
---
I am always a bit hesitant to add feature
pjfanning commented on pull request #15:
URL:
https://github.com/apache/logging-log4j-scala/pull/15#issuecomment-1014919650
@vy I just added https://github.com/apache/logging-log4j2/pull/715 - I will
create a 2nd PR (for master) when the first one is merged.
--
This is an automated mess
vy commented on pull request #15:
URL:
https://github.com/apache/logging-log4j-scala/pull/15#issuecomment-1014915107
@pjfanning, thanks for the contribution. For
[scala-api.html](https://logging.apache.org/log4j/2.x/manual/scala-api.html),
search for `scala-api.*` files in [Log4j 2](/apac
vy merged pull request #15:
URL: https://github.com/apache/logging-log4j-scala/pull/15
--
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: notificatio
[
https://issues.apache.org/jira/browse/LOG4J2-3232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Sicker resolved LOG4J2-3232.
-
Resolution: Duplicate
Already handled in linked epic.
> Log4j 3.0 - Better Java SE modules depe
[
https://issues.apache.org/jira/browse/LOG4J2-109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Sicker resolved LOG4J2-109.
Resolution: Won't Fix
Nearly 10 years later, this is no longer a desirable feature to publish. Ther
vy merged pull request #14:
URL: https://github.com/apache/logging-log4j-scala/pull/14
--
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: notificatio
[
https://issues.apache.org/jira/browse/LOG4J2-1000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17477445#comment-17477445
]
Matt Sicker commented on LOG4J2-1000:
-
Is this feature still relevant? I can do a ba
[
https://issues.apache.org/jira/browse/LOG4J2-1305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17477443#comment-17477443
]
Matt Sicker commented on LOG4J2-1305:
-
I wonder if this feature would make for a goo
[
https://issues.apache.org/jira/browse/LOG4J2-1397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17477442#comment-17477442
]
Matt Sicker commented on LOG4J2-1397:
-
Is this still required now that layouts exten
vy merged pull request #691:
URL: https://github.com/apache/logging-log4j2/pull/691
--
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-
[
https://issues.apache.org/jira/browse/LOG4J2-1473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Sicker resolved LOG4J2-1473.
-
Resolution: Fixed
In the past couple months, every project at Apache now knows more about this
[
https://issues.apache.org/jira/browse/LOG4J2-3344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17477438#comment-17477438
]
Volkan Yazici commented on LOG4J2-3344:
---
This has the potential to be a killer fea
[
https://issues.apache.org/jira/browse/LOG4J2-2404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Sicker resolved LOG4J2-2404.
-
Resolution: Duplicate
> Need a NTEventLogAppender.amd64.dll for Log4j 2
> --
[
https://issues.apache.org/jira/browse/LOG4J2-1691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Sicker resolved LOG4J2-1691.
-
Resolution: Fixed
This was generally handled during the migration to SBT and recent releases.
>
[
https://issues.apache.org/jira/browse/LOG4J2-1777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Sicker resolved LOG4J2-1777.
-
Resolution: Won't Fix
The Log4j Boot concept can be superseded by the increased modularization b
[
https://issues.apache.org/jira/browse/LOG4J2-1775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Sicker resolved LOG4J2-1775.
-
Resolution: Won't Fix
The Log4j Boot concept can be superseded by the increased modularization b
[
https://issues.apache.org/jira/browse/LOG4J2-1783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Sicker resolved LOG4J2-1783.
-
Resolution: Won't Fix
The Log4j Boot concept can be superseded by the increased modularization b
[
https://issues.apache.org/jira/browse/LOG4J2-1792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17477431#comment-17477431
]
Matt Sicker commented on LOG4J2-1792:
-
I think this might be supported now in a diff
[
https://issues.apache.org/jira/browse/LOG4J2-1797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17477429#comment-17477429
]
Matt Sicker commented on LOG4J2-1797:
-
Another feature potentially useful to introdu
[
https://issues.apache.org/jira/browse/LOG4J2-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17477428#comment-17477428
]
Matt Sicker commented on LOG4J2-1870:
-
This might be a good idea to incorporate for
carterkozak closed pull request #714:
URL: https://github.com/apache/logging-log4j2/pull/714
--
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: notif
[
https://issues.apache.org/jira/browse/LOG4J2-2080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Sicker resolved LOG4J2-2080.
-
Fix Version/s: 2.13.0
Resolution: Fixed
This was finished by 2.13.0 when we started requi
[
https://issues.apache.org/jira/browse/LOG4J2-2653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Sicker updated LOG4J2-2653:
Fix Version/s: (was: 2.16.0)
> Migrate to JUnit 5
> --
>
> Key
[
https://issues.apache.org/jira/browse/LOG4J2-2653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17477422#comment-17477422
]
Matt Sicker commented on LOG4J2-2653:
-
Added CassandraFixture in master to replace o
[
https://issues.apache.org/jira/browse/LOG4J2-2699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Sicker resolved LOG4J2-2699.
-
Resolution: Duplicate
> Please reduce the size of log4j-core.jar
> -
[
https://issues.apache.org/jira/browse/LOG4J2-2795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Sicker updated LOG4J2-2795:
Epic Link: LOG4J2-2803
> Make LogManager/LoggerContext creation time reasonable
>
[
https://issues.apache.org/jira/browse/LOG4J2-2802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Sicker updated LOG4J2-2802:
Epic Link: LOG4J2-2226
> Log4j-core must only require java.base
>
[
https://issues.apache.org/jira/browse/LOG4J2-3232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17477419#comment-17477419
]
Ralph Goers commented on LOG4J2-3232:
-
This should really just be closed as a duplic
[
https://issues.apache.org/jira/browse/LOG4J2-2854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17477418#comment-17477418
]
Matt Sicker commented on LOG4J2-2854:
-
This is in master, though it's still under de
[
https://issues.apache.org/jira/browse/LOG4J2-2862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17477417#comment-17477417
]
Matt Sicker commented on LOG4J2-2862:
-
Updating this for JsonTemplateLayout as this
[
https://issues.apache.org/jira/browse/LOG4J2-2862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Sicker updated LOG4J2-2862:
Component/s: JsonTemplateLayout
> Add Masking to JsonTemplateLayout
>
[
https://issues.apache.org/jira/browse/LOG4J2-2862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Sicker updated LOG4J2-2862:
Summary: Add Masking to JsonTemplateLayout (was: Add Masking to JsonLayout)
> Add Masking to Json
[
https://issues.apache.org/jira/browse/LOG4J2-3065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Sicker resolved LOG4J2-3065.
-
Fix Version/s: 2.17.2
Assignee: Volkan Yazici
Resolution: Fixed
Fixed in release
[
https://issues.apache.org/jira/browse/LOG4J2-3210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Sicker resolved LOG4J2-3210.
-
Fix Version/s: 2.17.0
Resolution: Fixed
This was fixed in 2.17.0 by removing the attempt
[
https://issues.apache.org/jira/browse/LOG4J2-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Sicker resolved LOG4J2-3223.
-
Resolution: Fixed
> Log4J2 project page displays wrong syntax for "nolookups"
>
[
https://issues.apache.org/jira/browse/LOG4J2-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17477411#comment-17477411
]
Matt Sicker commented on LOG4J2-3228:
-
Some potential breaking changes this would in
[
https://issues.apache.org/jira/browse/LOG4J2-3232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Sicker updated LOG4J2-3232:
Epic Link: LOG4J2-2226
> Log4j 3.0 - Better Java SE modules dependency
> -
[
https://issues.apache.org/jira/browse/LOG4J2-3260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17477406#comment-17477406
]
Matt Sicker commented on LOG4J2-3260:
-
We've enabled force-push protection on master
[
https://issues.apache.org/jira/browse/LOG4J2-3269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Sicker resolved LOG4J2-3269.
-
Resolution: Information Provided
> Method To Find Log4j Version on Windows Servers
> ---
[
https://issues.apache.org/jira/browse/LOG4J2-3279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Sicker resolved LOG4J2-3279.
-
Resolution: Information Provided
Please see above response. If there are further questions about
[
https://issues.apache.org/jira/browse/LOG4J2-3300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17477403#comment-17477403
]
Matt Sicker commented on LOG4J2-3300:
-
This is partially implemented in master so fa
[
https://issues.apache.org/jira/browse/LOG4J2-3314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17477401#comment-17477401
]
Matt Sicker commented on LOG4J2-3314:
-
I'm not able to reproduce this problem.
{{$
[
https://issues.apache.org/jira/browse/LOG4J2-3320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Sicker resolved LOG4J2-3320.
-
Resolution: Information Provided
Your linked configuration looks fine. The only lookup you're us
[
https://issues.apache.org/jira/browse/LOG4J2-3224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Sicker resolved LOG4J2-3224.
-
Resolution: Information Provided
> Log4j 2.13.0
>
>
> Key: LOG4J2-3
[
https://issues.apache.org/jira/browse/LOG4J2-3343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Sicker resolved LOG4J2-3343.
-
Fix Version/s: 2.17.2
Resolution: Fixed
Added to release-2.x and master. Implemented this
[
https://issues.apache.org/jira/browse/LOG4J2-3343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17477387#comment-17477387
]
ASF subversion and git services commented on LOG4J2-3343:
-
Commi
[
https://issues.apache.org/jira/browse/LOG4J2-3343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17477388#comment-17477388
]
ASF subversion and git services commented on LOG4J2-3343:
-
Commi
[
https://issues.apache.org/jira/browse/LOG4J2-3343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17477389#comment-17477389
]
ASF subversion and git services commented on LOG4J2-3343:
-
Commi
[
https://issues.apache.org/jira/browse/LOG4J2-3343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on LOG4J2-3343 started by Matt Sicker.
---
> Add ability to use exclusion pattern filter on Map Resolver keys
>
[
https://issues.apache.org/jira/browse/LOG4J2-3343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Sicker reassigned LOG4J2-3343:
---
Assignee: Matt Sicker
> Add ability to use exclusion pattern filter on Map Resolver keys
>
Carter Kozak created LOG4J2-3345:
Summary: log4j-jpl must handle parameters as MessageFormat args
Key: LOG4J2-3345
URL: https://issues.apache.org/jira/browse/LOG4J2-3345
Project: Log4j 2
Issu
carterkozak opened a new pull request #712:
URL: https://github.com/apache/logging-log4j2/pull/712
These tests provide additional coverage in the event parameters
are passed through, demonstrating how JUL formatters are likely
to misinterpret such LogRecords.
--
This is an automated
BUILD UNSTABLE
Build URL
https://ci-builds.apache.org/job/Logging/job/log4j/job/release-2.x/753/
Project:
release-2.x
Date of build:
Mon, 17 Jan 2022 17:08:45 +
Build duration:
1 hr 36 min and counting
JUnit Tests
Name: (root) Failed: 0 test(s),
rm5248 commented on pull request #103:
URL: https://github.com/apache/logging-log4cxx/pull/103#issuecomment-1014708051
looks good to me.
I prefer to merge into master and then merge master into next_stable
manually once I have a few changes(so I don't have to do the same fix twice),
jvz commented on a change in pull request #683:
URL: https://github.com/apache/logging-log4j2/pull/683#discussion_r786137086
##
File path:
log4j-core/src/main/java/org/apache/logging/log4j/core/appender/SyslogAppender.java
##
@@ -104,6 +104,9 @@
@PluginElement("Logger
ppkarwasz closed pull request #706:
URL: https://github.com/apache/logging-log4j2/pull/706
--
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 #706:
URL: https://github.com/apache/logging-log4j2/pull/706#issuecomment-1014676863
I'll move the tests to the PRs that actually fix bugs, then. Thanks.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log
garydgregory edited a comment on pull request #706:
URL: https://github.com/apache/logging-log4j2/pull/706#issuecomment-1014655999
Hi @ppkarwasz
Failing a build is not going to be acceptable IMO. Because different team
members work at different times and availability, like me, I don't w
garydgregory commented on pull request #706:
URL: https://github.com/apache/logging-log4j2/pull/706#issuecomment-1014655999
Hi @ppkarwasz
Failing a build is not going to be acceptable IMO. Because different team
members work at different times and availability, like me, I don't want to
ppkarwasz commented on pull request #711:
URL: https://github.com/apache/logging-log4j2/pull/711#issuecomment-1014635782
This modification is tested by
`AbstractLog4j1ConfigurationTest.testConsoleXmlLayout()` I submitted in #706.
That PR is hard to split into parts without generating many
rm5248 commented on pull request #105:
URL: https://github.com/apache/logging-log4cxx/pull/105#issuecomment-1014550892
One (potential) issue that I see here is that because the variables are
still declared as `static`, they may get destroyed when the application is
exiting(but another thre
garydgregory commented on pull request #700:
URL: https://github.com/apache/logging-log4j2/pull/700#issuecomment-1014541566
> Are the test failures related to this change?
I just started a re-run of all the jobs. Let's see if the build passes.
--
This is an automated message from t
garydgregory commented on a change in pull request #706:
URL: https://github.com/apache/logging-log4j2/pull/706#discussion_r786004843
##
File path:
log4j-1.2-api/src/test/java/org/apache/log4j/config/AbstractLog4j1ConfigurationTest.java
##
@@ -0,0 +1,264 @@
+/*
+ * Licensed to
garydgregory commented on pull request #707:
URL: https://github.com/apache/logging-log4j2/pull/707#issuecomment-1014536381
Hi @ppkarwasz
You need tests to fail without these main changes to show the main changes
actually fix something. Otherwise, future changes might just reintroduce t
garydgregory commented on pull request #708:
URL: https://github.com/apache/logging-log4j2/pull/708#issuecomment-1014529504
"Since not all Log4j 1.x component builders extend AbstractBuilder,
BuilderManager#createBuilder throws a ClassCastException when instantiating
some of them."
garydgregory commented on a change in pull request #709:
URL: https://github.com/apache/logging-log4j2/pull/709#discussion_r785996466
##
File path:
log4j-1.2-api/src/main/java/org/apache/log4j/builders/AbstractBuilder.java
##
@@ -91,7 +91,11 @@ protected String getValueAttribu
1 - 100 of 103 matches
Mail list logo
