[
https://issues.apache.org/jira/browse/LOG4J2-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma updated LOG4J2-2059:
Description:
Refactor classes in the core.net.ssl package so that an SSL context can be
created wi
[
https://issues.apache.org/jira/browse/LOG4J2-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma updated LOG4J2-2059:
Description:
Refactor classes in the core.net.ssl package so that an SSL context can be
created wi
[
https://issues.apache.org/jira/browse/LOG4J2-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma updated LOG4J2-2059:
Priority: Minor (was: Major)
> Refactor classes in core.net.ssl to allow non-KeyStore Providers
>
It would be impossible to support Logback without pulling in slf4j-api, and
the extra jars is what causes the perception of a problem.
On 26 September 2017 at 03:20, Remko Popma wrote:
> Sounds to me that Ralph's analysis shows that doing the binding ourselves
> may not be worth doing since we c
[
https://issues.apache.org/jira/browse/LOG4J2-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikael Ståldal resolved LOG4J2-1694.
Resolution: Fixed
Fix Version/s: 2.10.0
In Git master, please verify and close.
> A
[
https://issues.apache.org/jira/browse/LOG4J2-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16181490#comment-16181490
]
ASF subversion and git services commented on LOG4J2-1694:
-
Commit
Github user asfgit closed the pull request at:
https://github.com/apache/logging-log4j2/pull/110
---
[
https://issues.apache.org/jira/browse/LOG4J2-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16181484#comment-16181484
]
Mikael Ståldal commented on LOG4J2-2056:
I once made the log4j-liquibase module.
[
https://issues.apache.org/jira/browse/LOG4J2-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikael Ståldal updated LOG4J2-1694:
---
Affects Version/s: 2.9.1
2.9.0
> Allow to easily add fields with fixed
Github user mikaelstaldal commented on the issue:
https://github.com/apache/logging-log4j2/pull/110
2.9.1 is now released, and the next release will (most likely) be 2.10.0
which will include this. We have no date set for that release, but historically
there has been at least three mo
[
https://issues.apache.org/jira/browse/LOG4J2-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikael Ståldal reassigned LOG4J2-1694:
--
Assignee: Mikael Ståldal
> Allow to easily add fields with fixed values to JSON output
[
https://issues.apache.org/jira/browse/LOG4J2-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16180978#comment-16180978
]
ASF subversion and git services commented on LOG4J2-2054:
-
Commit
[
https://issues.apache.org/jira/browse/LOG4J2-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma resolved LOG4J2-1896.
-
Resolution: Fixed
I created a separate ticket LOG4J2-2059 to deal with non-KeyStore based
provid
Remko Popma created LOG4J2-2059:
---
Summary: Refactor classes in core.net.ssl to allow non-KeyStore
Providers
Key: LOG4J2-2059
URL: https://issues.apache.org/jira/browse/LOG4J2-2059
Project: Log4j 2
[
https://issues.apache.org/jira/browse/LOG4J2-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16180851#comment-16180851
]
Gary Gregory commented on LOG4J2-1896:
--
The SSL and JMS CMs count on being able to r
[
https://issues.apache.org/jira/browse/LOG4J2-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16180775#comment-16180775
]
Remko Popma edited comment on LOG4J2-1896 at 9/26/17 2:01 PM:
-
[
https://issues.apache.org/jira/browse/LOG4J2-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16180775#comment-16180775
]
Remko Popma commented on LOG4J2-1896:
-
The most general interface for SSL seems to be
[
https://issues.apache.org/jira/browse/LOG4J2-2058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dean Wookey updated LOG4J2-2058:
Description:
When using the JUL log manager, setting the java.locale.providers property to
"HOST"
Dean Wookey created LOG4J2-2058:
---
Summary: java.locale.providers set to HOST causes Log4j2 to crash
in Java 9
Key: LOG4J2-2058
URL: https://issues.apache.org/jira/browse/LOG4J2-2058
Project: Log4j 2
[
https://issues.apache.org/jira/browse/LOG4J2-2058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dean Wookey updated LOG4J2-2058:
Description:
When using the JUL log manager, setting the java.locale.providers property to
"HOST"
Sounds to me that Ralph's analysis shows that doing the binding ourselves may
not be worth doing since we can't get an advantage by either improving people's
perception nor improve performance. Unless I'm missing something.
> On Sep 26, 2017, at 16:34, Mikael Ståldal wrote:
>
> I don't thin
I don't think we should support binding to Logback specifically. We
should support binding to any SLF4J implementation (including Logback).
We should probably test this with Logback though, since it's one of the
most popular SLF4J implementations.
On 2017-09-26 03:58, Matt Sicker wrote:
Woul
22 matches
Mail list logo
