Yes, I started doing that when I realized it didn’t solve anything. We still
would require the slf4j-api jar to get the interfaces and MDC unless we were to
use Reflection, which I think would be a very bad idea. So the perception would
still be there that there is extra overhead.
Ralph
> On S
Would it be possible to make a log4j-api provider that binds directly to
logback instead?
On 25 September 2017 at 18:54, Ralph Goers
wrote:
> I have been looking at the log4j-to-slf4j binding and am rethinking
> changing it. There really isn’t much to SLF4J to begin with. Unlike Log4j
> 2, Logg
I have been looking at the log4j-to-slf4j binding and am rethinking changing
it. There really isn’t much to SLF4J to begin with. Unlike Log4j 2, Logger is
an interface; the whole implementation is delegated. All SLF4J really does is
perform the binding between it and the implementation. So what
Thanks for reviewing.
Good catch, a null check is needed to prevent NPEs.
But null passwords are possible so perhaps make it like this:
return password == null ? null : password.toCharArray();
> On Sep 26, 2017, at 1:08, Gary Gregory wrote:
>
>> On Mon, Sep 25, 2017 at 10:00 AM, wrote:
>>
[
https://issues.apache.org/jira/browse/LOG4J2-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers updated LOG4J2-2056:
Description:
To fully support Java 9 all Log4j jars must (at least) be packaged as automatic
modul
[
https://issues.apache.org/jira/browse/LOG4J2-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers updated LOG4J2-2056:
Description:
To fully support Java 9 all Log4j jars must (at least) be packaged as automatic
modul
[
https://issues.apache.org/jira/browse/LOG4J2-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16179761#comment-16179761
]
Ralph Goers commented on LOG4J2-2056:
-
[~scolebou...@joda.org] Thanks for taking a lo
I am fine with adding new features.
Ralph
> On Sep 25, 2017, at 12:28 PM, Mikael Ståldal wrote:
>
> So, now we have released 2.9.1, and JDK 9 GA is out. Do we need an 2.9.2, or
> can we go on and add features for 2.10.0?
>
>
> On 2017-09-14 22:27, Ralph Goers wrote:
>> I plan on doing the re
[
https://issues.apache.org/jira/browse/LOG4J2-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16179640#comment-16179640
]
Stephen Colebourne commented on LOG4J2-2056:
I've had a quick look. The api a
So, now we have released 2.9.1, and JDK 9 GA is out. Do we need an
2.9.2, or can we go on and add features for 2.10.0?
On 2017-09-14 22:27, Ralph Goers wrote:
I plan on doing the release build this weekend. Please hold off on merging new
features until after that. I agree with your plan.
Ral
[
https://issues.apache.org/jira/browse/LOG4J2-1944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Weian Deng updated LOG4J2-1944:
---
Attachment: LOG4J2-1944.patch
> Should suppress message "ERROR No log4j2 configuration file found..."
On Mon, Sep 25, 2017 at 10:00 AM, wrote:
> Repository: logging-log4j2
> Updated Branches:
> refs/heads/master a73fce2e7 -> 08077cba3
>
>
> LOG4J2-2054 Provide ways to configure SSL that avoid plain-text passwords
> in the log4j configuration. The configuration may now specify a system
> environ
[
https://issues.apache.org/jira/browse/LOG4J2-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16179230#comment-16179230
]
ASF subversion and git services commented on LOG4J2-2054:
-
Commit
[
https://issues.apache.org/jira/browse/LOG4J2-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma closed LOG4J2-2054.
---
Resolution: Fixed
> Provide ways to configure SSL that avoid plain-text passwords in the log4j
> con
[
https://issues.apache.org/jira/browse/LOG4J2-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16179218#comment-16179218
]
ASF subversion and git services commented on LOG4J2-2054:
-
Commit
Understood about the log4j-to-slf4j diagram.
About updating the performance page, I haven't been able to spend much time on
Log4j2 recently. When I did have time it has gone mostly into bug fixes.
If you have done this before you probably know this, but doing these
performance investigations
[
https://issues.apache.org/jira/browse/LOG4J2-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16178663#comment-16178663
]
Daan Hoogland edited comment on LOG4J2-1971 at 9/25/17 7:34 AM:
---
[
https://issues.apache.org/jira/browse/LOG4J2-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16178663#comment-16178663
]
Daan Hoogland commented on LOG4J2-1971:
---
People, I am getting this outside OSGi con
18 matches
Mail list logo
