Re: log4j-to-slf4j

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

Re: log4j-to-slf4j

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

Re: logging-log4j2 git commit: LOG4J2-2054 Provide ways to configure SSL that avoid plain-text passwords in the log4j configuration. The configuration may now specify a system environment variable tha

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

[jira] [Updated] (LOG4J2-2056) Modularize Log4j as automatic modules

[ 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

[jira] [Updated] (LOG4J2-2056) Modularize Log4j as automatic modules

[ 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

[jira] [Commented] (LOG4J2-2056) Modularize Log4j as automatic modules

[ https://issues.apache.org/jira/browse/LOG4J2-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16179761#comment-16179761 ] Ralph Goers commented on LOG4J2-2056: - [~scolebou...@joda.org] Thanks for taking a look. Your

Re: Log4J 2.9.1 release

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

[jira] [Commented] (LOG4J2-2056) Modularize Log4j as automatic modules

[ https://issues.apache.org/jira/browse/LOG4J2-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16179640#comment-16179640 ] Stephen Colebourne commented on LOG4J2-2056: I've had a quick look. The api and log4j1.2 jars

Re: Log4J 2.9.1 release

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.

[jira] [Updated] (LOG4J2-1944) Should suppress message "ERROR No log4j2 configuration file found..." when programmatic API is used to config log4j.

[ 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

[jira] [Commented] (LOG4J2-2054) Provide ways to configure SSL that avoid plain-text passwords in the log4j configuration

[ https://issues.apache.org/jira/browse/LOG4J2-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16179230#comment-16179230 ] ASF subversion and git services commented on LOG4J2-2054: - Commit

[jira] [Closed] (LOG4J2-2054) Provide ways to configure SSL that avoid plain-text passwords in the log4j configuration

[ 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 >

[jira] [Commented] (LOG4J2-2054) Provide ways to configure SSL that avoid plain-text passwords in the log4j configuration

[ https://issues.apache.org/jira/browse/LOG4J2-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16179218#comment-16179218 ] ASF subversion and git services commented on LOG4J2-2054: - Commit

Re: log4j-to-slf4j

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

[jira] [Comment Edited] (LOG4J2-1971) ClassCastException: org.eclipse.osgi.internal.loader.SystemBundleLoader$1 cannot be cast to java.lang.ClassLoader

[ https://issues.apache.org/jira/browse/LOG4J2-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16178663#comment-16178663 ] Daan Hoogland edited comment on LOG4J2-1971 at 9/25/17 7:34 AM: People, I

[jira] [Commented] (LOG4J2-1971) ClassCastException: org.eclipse.osgi.internal.loader.SystemBundleLoader$1 cannot be cast to java.lang.ClassLoader

[ https://issues.apache.org/jira/browse/LOG4J2-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16178663#comment-16178663 ] Daan Hoogland commented on LOG4J2-1971: --- People, I am getting this outside OSGi context. I try to

[jira] [Closed] (LOG4J2-2052) Disable thread name caching by default

[ https://issues.apache.org/jira/browse/LOG4J2-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Berindei closed LOG4J2-2052. Verified on master, thanks! > Disable thread name caching by default >