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

Re: log4j-to-slf4j

Yes, that is what we would want to do. BTW - I mentioned it a while ago but is there any chance we can get updated performance charts? The charts are for Log4j 2.6 vs Logback 1.1.7. Logback is now at 1.1.11 and 1.2.3. I am not really clear on what is different between 1.1.x and 1.2.x. Ralph

Re: log4j-to-slf4j

Ok I see now. It would certainly be good to have more ammunition to argue for using the Log4j2 API directly. Comments on StackOverflow https://stackoverflow.com/a/41500347/1446916 show some people perceive the log4j-to-slf4j module as a facade for a facade. If we bind directly, perhaps I sho

[jira] [Closed] (LOG4J2-2057) Support SLF4J 1.8 binding mechanism

[ https://issues.apache.org/jira/browse/LOG4J2-2057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers closed LOG4J2-2057. --- Resolution: Fixed Fix Version/s: 2.9.2 Fix has been committed. > Support SLF4J 1.8 binding me

[jira] [Commented] (LOG4J2-2057) Support SLF4J 1.8 binding mechanism

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

[jira] [Commented] (LOG4J2-1896) Update classes in org.apache.logging.log4j.core.net.ssl in APIs from String to char[] for passwords

[ https://issues.apache.org/jira/browse/LOG4J2-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16178460#comment-16178460 ] Remko Popma commented on LOG4J2-1896: - (Note to self, still looking into this) Useful

Fwd: log4j-to-slf4j

Well, SLF4J recently changed the binding mechanism with 1.8 in order to comply with Java 9. It isn’t likely to do it again any time soon. What we would “solve” is that now it is log4j-api -> log4j-to-slf4j -> slf4j-api -> logging implementation. With this change it would be log4j-api -> log4j

Re: log4j-to-slf4j

That's certainly possible. The trade off is that we'd need to track the SLF4J binding mechanism and update our implementation when this binding mechanism changes. What problem are we trying to solve? Remko > On Sep 25, 2017, at 7:16, Ralph Goers wrote: > > In looking at the implementations

log4j-to-slf4j

In looking at the implementations of log4j-slf4j-impl and log4j-to-slf4j is strikes me that log4j-to-slf4j is binding to the SLF4J API while log4j-slf4j-impl is binding the SFL4J API to the log4j implementation using SLF4J’s binding mechanism. So it seems to me that instead of having log4j-to-s

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

[ https://issues.apache.org/jira/browse/LOG4J2-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16178266#comment-16178266 ] Ralph Goers edited comment on LOG4J2-2056 at 9/24/17 4:25 PM: -

[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&focusedCommentId=16178268#comment-16178268 ] Matt Sicker commented on LOG4J2-2056: - Got it. Package names as listed right now LGTM

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

[ https://issues.apache.org/jira/browse/LOG4J2-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16178266#comment-16178266 ] Ralph Goers edited comment on LOG4J2-2056 at 9/24/17 4:23 PM: -

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

[ https://issues.apache.org/jira/browse/LOG4J2-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16178266#comment-16178266 ] Ralph Goers edited comment on LOG4J2-2056 at 9/24/17 4:23 PM: -

[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&focusedCommentId=16178266#comment-16178266 ] Ralph Goers commented on LOG4J2-2056: - Technically they could but I would find that c

[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&focusedCommentId=16178265#comment-16178265 ] Matt Sicker commented on LOG4J2-2056: - Can both slf4j modules have the same name sinc

[jira] [Created] (LOG4J2-2057) Support SLF4J 1.8 binding mechanism

Ralph Goers created LOG4J2-2057: --- Summary: Support SLF4J 1.8 binding mechanism Key: LOG4J2-2057 URL: https://issues.apache.org/jira/browse/LOG4J2-2057 Project: Log4j 2 Issue Type: Improvement

[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&focusedCommentId=16178239#comment-16178239 ] Ralph Goers commented on LOG4J2-2056: - OK. I changed the table. > Modularize Log4j a

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

[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&focusedCommentId=16178222#comment-16178222 ] Gary Gregory commented on LOG4J2-2056: -- I kind of like the dot matching the dash in

[jira] [Updated] (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 updated LOG4J2-2054: Description: Following up on LOG4J2-1896, currently SecureSocketAppender can only be configured by

[jira] [Updated] (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 updated LOG4J2-2054: Summary: Provide ways to configure SSL that avoid plain-text passwords in the log4j configuration

Jenkins build is back to normal : Log4j 2.x #3092

See

[jira] [Commented] (LOG4J2-1896) Update classes in org.apache.logging.log4j.core.net.ssl in APIs from String to char[] for passwords

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

Build failed in Jenkins: Log4j 2.x #3091

See Changes: [rpopma] LOG4J2-1896 limit visibility of MemoryPasswordProvider implementation -- [...truncated 115.89 KB...] missing type arguments for generic class Class wh

[jira] [Commented] (LOG4J2-1896) Update classes in org.apache.logging.log4j.core.net.ssl in APIs from String to char[] for passwords

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

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

[ https://issues.apache.org/jira/browse/LOG4J2-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16178143#comment-16178143 ] Ralph Goers edited comment on LOG4J2-2056 at 9/24/17 10:34 AM:

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

[ https://issues.apache.org/jira/browse/LOG4J2-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16178143#comment-16178143 ] Ralph Goers edited comment on LOG4J2-2056 at 9/24/17 10:32 AM:

[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&focusedCommentId=16178143#comment-16178143 ] Ralph Goers commented on LOG4J2-2056: - If they want to release Log4J 1 then they woul

[jira] [Resolved] (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 ] Remko Popma resolved LOG4J2-2052. - Resolution: Fixed Fix Version/s: 2.10.0 Fixed in master. Please verify and close. > Disab

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

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

[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&focusedCommentId=16178121#comment-16178121 ] Remko Popma commented on LOG4J2-2056: - Is it a good idea to use the below? |log4j-1.

Java 9 module names

I have created https://issues.apache.org/jira/browse/LOG4J2-2056 to identify the module names we want to use. The effort to resolve this issue will be to add the “Automatic-Module-Name” header to the jar manifest for each of the maven modules

[jira] [Assigned] (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 reassigned LOG4J2-2056: --- Assignee: Ralph Goers > Modularize Log4j as automatic modules >

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

Ralph Goers created LOG4J2-2056: --- Summary: Modularize Log4j as automatic modules Key: LOG4J2-2056 URL: https://issues.apache.org/jira/browse/LOG4J2-2056 Project: Log4j 2 Issue Type: New Feature