Re: Automatic module names

While true that would be immensely confusing to users I think. However, if two modules have the same packages in them you will get an error at runtime. "Now consider again the key restriction that a package must be found in one and only one module. This restriction applies to hidden packages as

Re: Automatic module names

Isn't it the opposite? Giving them the same module name will prevents them from being used together, which is what we want: http://blog.joda.org/2017/04/java-se-9-jpms-module-naming.html?m=1 "JPMS will simply refuse to start a modulepath where two modules have the same name, even if they contain

Re: Random failure in AsyncLoggerAndAsyncAppenderTest

I've looked at this before but couldn't figure it out. I'll take another look. (Shameless plug) Every java main() method deserves http://picocli.info > On Sep 12, 2017, at 9:00, Matt Sicker wrote: > > I'm pretty sure I've seen that failure (or something similar at least) > several times before

Re: Automatic module names

Actually, re-reading this again makes it clear to me that log4j-slf4j-impl and log4j-to-slf4j SHOULD use the same package name as it prevents them from both being present at the same time. Obviously, their module names still have to be different but this could mean the code doesn’t really need t

Re: Automatic module names

You should read (or re-read) this - http://blog.joda.org/2017/04/java-se-9-jpms-module-naming.html . I believe it is the most likely standard to be adopted. Ralph > On Sep 11, 2017, at 6:26 PM, Matt Sicker wrote: > > Is it possi

Re: Log4J 2.9.1 release

OK. The module is commented out along with the update to changes.xml. Ralph > On Sep 11, 2017, at 4:56 PM, Matt Sicker wrote: > > Sounds good to me. I'd rather get some more features in for 2.10.0 first. > > On 11 September 2017 at 18:33, Gary Gregory wrote: > >> On Mon, Sep 11, 2017 at 5:19

[jira] [Updated] (LOG4J2-2025) Support Tomcat JULI's per-webapp JUL logging by implementing java.util.logging.Handler

[ https://issues.apache.org/jira/browse/LOG4J2-2025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-2025: Fix Version/s: (was: 2.9.1) 2.10.0 > Support Tomcat JULI's per-webapp JUL lo

[jira] [Commented] (LOG4J2-2025) Support Tomcat JULI's per-webapp JUL logging by implementing java.util.logging.Handler

[ https://issues.apache.org/jira/browse/LOG4J2-2025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16162462#comment-16162462 ] Ralph Goers commented on LOG4J2-2025: - Reopening since we are not going to include th

[jira] [Reopened] (LOG4J2-2025) Support Tomcat JULI's per-webapp JUL logging by implementing java.util.logging.Handler

[ https://issues.apache.org/jira/browse/LOG4J2-2025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers reopened LOG4J2-2025: - > Support Tomcat JULI's per-webapp JUL logging by implementing > java.util.logging.Handler > ---

Re: Build failed in Jenkins: Log4j 2.x #3052

On Sep 11, 2017 21:43, "Matt Sicker" wrote: Looking closer, it says it cannot find the symbol, not the class. Missing import statement. Yep, already fixed a while back. :-) Gary On 11 September 2017 at 21:36, Gary Gregory wrote: > I fixed something I broke... > > Gary > > On Sep 11, 2017 1

Re: Build failed in Jenkins: Log4j 2.x #3052

Looking closer, it says it cannot find the symbol, not the class. Missing import statement. On 11 September 2017 at 21:36, Gary Gregory wrote: > I fixed something I broke... > > Gary > > On Sep 11, 2017 18:08, "Matt Sicker" wrote: > > > I wonder if the jenkins java config changed at all. That c

Re: Build failed in Jenkins: Log4j 2.x #3052

I fixed something I broke... Gary On Sep 11, 2017 18:08, "Matt Sicker" wrote: > I wonder if the jenkins java config changed at all. That class is in > tools.jar I believe. > > On 11 September 2017 at 16:02, Gary Gregory > wrote: > > > Frak! What could cause the JConsolePlugin class to not be f

Re: Automatic module names

Is it possible to make the JPMS module names the same as the OSGi ones? The default OSGi naming scheme is basically: groupId: org.apache.logging.log4j, artifactId: log4j-foo becomes bundleId: org.apache.logging.log4j.foo On 11 September 2017 at 13:01, Gary Gregory wrote: > On Mon, Sep 11, 2017

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

See

Re: logging-log4j2 git commit: Revert "Remove unused imports."

Looks like only the ClientGuiJConsolePlugin class had the JConsole import that erred. You should be able to remove unused imports elsewhere, though. On 11 September 2017 at 19:00, wrote: > Repository: logging-log4j2 > Updated Branches: > refs/heads/master 471ef52e4 -> c9b1cf8c0 > > > Revert "R

[jira] [Commented] (LOG4J2-2041) 2.9.0 contains classes built to class version 53

[ https://issues.apache.org/jira/browse/LOG4J2-2041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16162266#comment-16162266 ] Matt Sicker commented on LOG4J2-2041: - Sounds like a bug report should be filed with

Re: Build failed in Jenkins: Log4j 2.x #3052

I wonder if the jenkins java config changed at all. That class is in tools.jar I believe. On 11 September 2017 at 16:02, Gary Gregory wrote: > Frak! What could cause the JConsolePlugin class to not be found? > > Gary > > -- Forwarded message -- > From: Apache Jenkins Server > Da

Re: Random failure in AsyncLoggerAndAsyncAppenderTest

I'm pretty sure I've seen that failure (or something similar at least) several times before. I believe the issue is essentially due to asynchronicity compared to JUnit. I wonder if JUnit 5 has async test support, though if we upgrade to that, then the tests will require Java 8. On 11 September 201

Re: Log4J 2.9.1 release

Sounds good to me. I'd rather get some more features in for 2.10.0 first. On 11 September 2017 at 18:33, Gary Gregory wrote: > On Mon, Sep 11, 2017 at 5:19 PM, Ralph Goers > wrote: > > > I’d be OK with not publishing log4j-appserver right now but I’d prefer to > > leave the module in but remove

Re: Log4J 2.9.1 release

On Mon, Sep 11, 2017 at 5:19 PM, Ralph Goers wrote: > I’d be OK with not publishing log4j-appserver right now but I’d prefer to > leave the module in but remove it from the parent pom so that it doesn’t > get built or deployed. Then I don’t think it has to be added to the release > notes even tho

Re: Log4J 2.9.1 release

I’d be OK with not publishing log4j-appserver right now but I’d prefer to leave the module in but remove it from the parent pom so that it doesn’t get built or deployed. Then I don’t think it has to be added to the release notes even though it technically is still part of the source release. Do

[jira] [Commented] (LOG4J2-2041) 2.9.0 contains classes built to class version 53

[ https://issues.apache.org/jira/browse/LOG4J2-2041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16162175#comment-16162175 ] Remko Popma commented on LOG4J2-2041: - Thanks for trying, Ralph! > 2.9.0 contains cl

[jira] [Commented] (LOG4J2-2031) Messages appear out of order in log file (was: Log4j2 log file not reflecting application log function calls)

[ https://issues.apache.org/jira/browse/LOG4J2-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16162169#comment-16162169 ] Remko Popma commented on LOG4J2-2031: - Thanks for pointing out that the documentation

[jira] [Commented] (LOG4J2-2031) Messages appear out of order in log file (was: Log4j2 log file not reflecting application log function calls)

[ https://issues.apache.org/jira/browse/LOG4J2-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16162158#comment-16162158 ] Remko Popma commented on LOG4J2-2031: - Hi Colin, The {{AsyncLoggerConfig.RingBufferS

Build failed in Jenkins: Log4j 2.x #3053

See Changes: [garydgregory] [LOG4J2-2046] Update Apache Commons Compress from 1.13 to 1.14. -- [...truncated 1.12 MB...] [INFO] [INFO] --- maven-resources-plugin:3.0.2:resourc

[jira] [Commented] (LOG4J2-2046) Update Apache Commons Compress from 1.13 to 1.14

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

[jira] [Closed] (LOG4J2-2046) Update Apache Commons Compress from 1.13 to 1.14

[ https://issues.apache.org/jira/browse/LOG4J2-2046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-2046. Resolution: Fixed Fix Version/s: 2.9.1 In git master. > Update Apache Commons Compress from

[jira] [Commented] (LOG4NET-575) log4net function having XXE vulnerability

[ https://issues.apache.org/jira/browse/LOG4NET-575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16162036#comment-16162036 ] Dominik Psenner commented on LOG4NET-575: - private(at)logging(dot)apache(dot)org

Fwd: Build failed in Jenkins: Log4j 2.x #3052

Frak! What could cause the JConsolePlugin class to not be found? Gary -- Forwarded message -- From: Apache Jenkins Server Date: Mon, Sep 11, 2017 at 2:17 PM Subject: Build failed in Jenkins: Log4j 2.x #3052 To: dev@logging.apache.org See

[jira] [Commented] (LOG4NET-575) log4net function having XXE vulnerability

[ https://issues.apache.org/jira/browse/LOG4NET-575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16161981#comment-16161981 ] karthik kumar balasundaram commented on LOG4NET-575: Sure Dominik,

[jira] [Commented] (LOG4NET-575) log4net function having XXE vulnerability

[ https://issues.apache.org/jira/browse/LOG4NET-575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16161928#comment-16161928 ] Dominik Psenner commented on LOG4NET-575: - Hi, Thanks for your report. We take s

Build failed in Jenkins: Log4j 2.x #3052

See -- [...truncated 1.12 MB...] [INFO] [INFO] --- maven-resources-plugin:3.0.2:resources (default-resources) @ log4j-taglib --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [IN

Random failure in AsyncLoggerAndAsyncAppenderTest

Just FYI: I am seeing this random but infrequent failure: [ERROR] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.62 s <<< FAILURE! - in org.apache.logging.log4j.core.async.AsyncLoggerThreadContextGarbageFreeTest [ERROR] testAsyncLogWritesToLog[GARBAGE_FREE BOTH_ALL_ASYNC_AND_MI

Re: Log4J 2.9.1 release

I don't think we should decide the versioning based on number of classes/methods/LOC added. We should decide it based on features added. A new feature warrants a bump in minor version, so the app server support should be in 2.10.0. We could also descope the app server support for now, and rele

Fwd: Build failed in Jenkins: Log4j 2.x #3051

A local build worked for me (mvn clean install), this looks a Nexus issue maybe. Gary -- Forwarded message -- From: Apache Jenkins Server Date: Mon, Sep 11, 2017 at 12:36 PM Subject: Build failed in Jenkins: Log4j 2.x #3051 To: dev@logging.apache.org See

Re: Build failed in Jenkins: Log4j 2.x #3051

Looks like you removed unused imports that aren’t unused? For some reason this feels like it has happened before. Ralph > On Sep 11, 2017, at 11:36 AM, Apache Jenkins Server > wrote: > > See > > > Changes: > > [

Build failed in Jenkins: Log4j 2.x #3051

See Changes: [garydgregory] [LOG4J2-2045] Update javax.mail from 1.5.6 to 1.6.0. [garydgregory] Remove unused imports. -- [...truncated 1.14 MB...] [INFO] [INFO] --- maven-re

[jira] [Created] (LOG4J2-2046) Update Apache Commons Compress from 1.13 to 1.14

Gary Gregory created LOG4J2-2046: Summary: Update Apache Commons Compress from 1.13 to 1.14 Key: LOG4J2-2046 URL: https://issues.apache.org/jira/browse/LOG4J2-2046 Project: Log4j 2 Issue Type

[jira] [Closed] (LOG4J2-2045) Update javax.mail from 1.5.6 to 1.6.0

[ https://issues.apache.org/jira/browse/LOG4J2-2045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-2045. Resolution: Fixed Fix Version/s: 2.9.1 Closing: In git master. > Update javax.mail from 1.5

[jira] [Commented] (LOG4J2-2045) Update javax.mail from 1.5.6 to 1.6.0

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

Re: Automatic module names

On Mon, Sep 11, 2017 at 11:27 AM, Ralph Goers wrote: > I know we discussed module names in the past and decided not to go the > route of modularizing now - in fact, we can’t until all of our dependencies > are modularized. However, we can (and probably should) add the automatic > module name as a

[jira] [Closed] (LOG4J2-2044) Update Apache Commons CSV from 1.4 to 1.5

[ https://issues.apache.org/jira/browse/LOG4J2-2044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-2044. Resolution: Cannot Reproduce Closing: In git master. > Update Apache Commons CSV from 1.4 to 1.5 >

[jira] [Commented] (LOG4J2-2044) Update Apache Commons CSV from 1.4 to 1.5

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

[jira] [Commented] (LOG4J2-2031) Messages appear out of order in log file (was: Log4j2 log file not reflecting application log function calls)

[ https://issues.apache.org/jira/browse/LOG4J2-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16161643#comment-16161643 ] Colin McDowell commented on LOG4J2-2031: I looked up the Log4j2 documentation.

Automatic module names

I know we discussed module names in the past and decided not to go the route of modularizing now - in fact, we can’t until all of our dependencies are modularized. However, we can (and probably should) add the automatic module name as a manifest entry to each of our jars. My understanding is tha

[jira] [Commented] (LOG4J2-2031) Messages appear out of order in log file (was: Log4j2 log file not reflecting application log function calls)

[ https://issues.apache.org/jira/browse/LOG4J2-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16161631#comment-16161631 ] Colin McDowell commented on LOG4J2-2031: Hi Remko, Not sure if our are directing

[jira] [Created] (LOG4J2-2045) Update javax.mail from 1.5.6 to 1.6.0

Gary Gregory created LOG4J2-2045: Summary: Update javax.mail from 1.5.6 to 1.6.0 Key: LOG4J2-2045 URL: https://issues.apache.org/jira/browse/LOG4J2-2045 Project: Log4j 2 Issue Type: Improveme

[jira] [Updated] (LOG4NET-575) log4net function having XXE vulnerability

[ https://issues.apache.org/jira/browse/LOG4NET-575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] karthik kumar balasundaram updated LOG4NET-575: --- Fix Version/s: (was: 2.0.9) 2.0.7 > log4net fu

[jira] [Created] (LOG4NET-575) log4net function having XXE vulnerability

karthik kumar balasundaram created LOG4NET-575: -- Summary: log4net function having XXE vulnerability Key: LOG4NET-575 URL: https://issues.apache.org/jira/browse/LOG4NET-575 Project: Log4ne

[jira] [Resolved] (LOG4J2-2043) Update Jackson from 2.9.0 to 2.9.1 (fix for Java 9)

[ https://issues.apache.org/jira/browse/LOG4J2-2043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory resolved LOG4J2-2043. -- Resolution: Fixed Closing: In git master. > Update Jackson from 2.9.0 to 2.9.1 (fix for Java 9

[jira] [Commented] (LOG4J2-2041) 2.9.0 contains classes built to class version 53

[ https://issues.apache.org/jira/browse/LOG4J2-2041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16161512#comment-16161512 ] Ralph Goers commented on LOG4J2-2041: - I should have added that specifying either -so

[jira] [Commented] (LOG4J2-2041) 2.9.0 contains classes built to class version 53

[ https://issues.apache.org/jira/browse/LOG4J2-2041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16161508#comment-16161508 ] Ralph Goers commented on LOG4J2-2041: - I tried compiling with a source of 9, target o

[jira] [Commented] (LOG4J2-2043) Update Jackson from 2.9.0 to 2.9.1 (fix for Java 9)

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

Re: Log4J 2.9.1 release

It was indeed my intention to have Jetty, JBoss, etc in that module. They are all mutually exclusive and presumably the dependencies would be provided so there really should be no conflict in having them all reside in the same module. I haven’t been pushing splitting up core as I have been advo

[jira] [Created] (LOG4J2-2044) Update Apache Commons CSV from 1.4 to 1.5

Gary Gregory created LOG4J2-2044: Summary: Update Apache Commons CSV from 1.4 to 1.5 Key: LOG4J2-2044 URL: https://issues.apache.org/jira/browse/LOG4J2-2044 Project: Log4j 2 Issue Type: Impro

Re: Log4J 2.9.1 release

I'm not sure how much of semantic versioning we really want to adopt or have adopted in the past. This is really about managing user's expectations when they update from one version to the next. In this case, a new module feels like a new feature. Yes, the new module adds only one class, but we ca

Re: Log4J 2.9.1 release

I thought about that, but it really is a pretty minor addition - it is one class. That said, if others feel that 2.10.0 is better I am happy to accommodate. Ralph > On Sep 11, 2017, at 8:31 AM, Gary Gregory wrote: > > Hi All, > > It seems to me that the recent addition of the log4j-appserver

Re: Log4J 2.9.1 release

Hi All, It seems to me that the recent addition of the log4j-appserver module requires a version bump to 2.10.0, not 2.9.1. Gary On Mon, Sep 11, 2017 at 8:25 AM, Matt Sicker wrote: > I still have my outstanding branch that didn't make it into 2.9.0 that's > ready to merge, though if you're rea

[jira] [Created] (LOG4J2-2043) Update Jackson from 2.9.0 to 2.9.1 (fix for Java 9)

Gary Gregory created LOG4J2-2043: Summary: Update Jackson from 2.9.0 to 2.9.1 (fix for Java 9) Key: LOG4J2-2043 URL: https://issues.apache.org/jira/browse/LOG4J2-2043 Project: Log4j 2 Issue T

[jira] [Commented] (LOG4J2-2041) 2.9.0 contains classes built to class version 53

[ https://issues.apache.org/jira/browse/LOG4J2-2041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16161353#comment-16161353 ] Matt Sicker commented on LOG4J2-2041: - If there were an easy way to compile for the e

Re: Log4J 2.9.1 release

I still have my outstanding branch that didn't make it into 2.9.0 that's ready to merge, though if you're ready to do a bugfix release like that, I'd rather wait for that first. On 11 September 2017 at 03:43, Mikael Ståldal wrote: > Sounds good. Have we fixed all discovered regressions and new b

[jira] [Commented] (LOG4J2-2041) 2.9.0 contains classes built to class version 53

[ https://issues.apache.org/jira/browse/LOG4J2-2041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16161292#comment-16161292 ] Remko Popma commented on LOG4J2-2041: - It just looked weird to me that one would be a

[jira] [Commented] (LOG4J2-1988) java.util.ConcurrentModificationException with AsyncLogger?

[ https://issues.apache.org/jira/browse/LOG4J2-1988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16161245#comment-16161245 ] Remko Popma commented on LOG4J2-1988: - The stack trace shows that the log event conta

[jira] [Commented] (LOG4J2-2041) 2.9.0 contains classes built to class version 53

[ https://issues.apache.org/jira/browse/LOG4J2-2041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16161240#comment-16161240 ] Ralph Goers commented on LOG4J2-2041: - Java 9 still supports -source and -target. The

[jira] [Commented] (LOG4J2-2041) 2.9.0 contains classes built to class version 53

[ https://issues.apache.org/jira/browse/LOG4J2-2041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16161193#comment-16161193 ] William Ferguson commented on LOG4J2-2041: -- That was how it was in JDK8 and belo

[jira] [Commented] (LOG4J2-2041) 2.9.0 contains classes built to class version 53

[ https://issues.apache.org/jira/browse/LOG4J2-2041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16161195#comment-16161195 ] William Ferguson commented on LOG4J2-2041: -- But I'm reading between the lines he

[jira] [Commented] (LOG4J2-2032) Curly braces in parameters are treated as placeholders

[ https://issues.apache.org/jira/browse/LOG4J2-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16161150#comment-16161150 ] Ralph Goers commented on LOG4J2-2032: - Sure. We would love to have the help! > Curl

[jira] [Assigned] (LOG4J2-1914) AsyncLogger and message formatting (ConcurrentModificationException)

[ https://issues.apache.org/jira/browse/LOG4J2-1914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reassigned LOG4J2-1914: --- Assignee: Remko Popma > AsyncLogger and message formatting (ConcurrentModificationException)

[jira] [Commented] (LOG4J2-2035) There is no such lib as disruptor-3.3.3

[ https://issues.apache.org/jira/browse/LOG4J2-2035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16161096#comment-16161096 ] Remko Popma commented on LOG4J2-2035: - I looked at the LMAX Disruptor Changelog page:

[jira] [Assigned] (LOG4J2-2035) There is no such lib as disruptor-3.3.3

[ https://issues.apache.org/jira/browse/LOG4J2-2035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reassigned LOG4J2-2035: --- Assignee: Remko Popma > There is no such lib as disruptor-3.3.3 > --

[jira] [Commented] (LOG4J2-2041) 2.9.0 contains classes built to class version 53

[ https://issues.apache.org/jira/browse/LOG4J2-2041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16161078#comment-16161078 ] Remko Popma commented on LOG4J2-2041: - [~william_f_au] It it possible to run javac wi

[jira] [Commented] (LOG4J2-1921) Getting ClassCastException while getting LoggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16160967#comment-16160967 ] William Ferguson commented on LOG4J2-1921: -- I am also interested in using log4j2

[jira] [Commented] (LOG4J2-2032) Curly braces in parameters are treated as placeholders

[ https://issues.apache.org/jira/browse/LOG4J2-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16160957#comment-16160957 ] Kostiantyn Shchepanovskyi commented on LOG4J2-2032: --- [~ralph.go...@dsle

Re: Log4J 2.9.1 release

Sounds good. Have we fixed all discovered regressions and new bugs in 2.9.0? On 2017-09-11 09:39, Apache wrote: I am thinking about doing the Log4J 2.9.1 release at the end of the week as there are a couple of bugs I'd like published by the time Java 9 is released. Ralph

[jira] [Commented] (LOG4J2-2041) 2.9.0 contains classes built to class version 53

[ https://issues.apache.org/jira/browse/LOG4J2-2041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16160913#comment-16160913 ] William Ferguson commented on LOG4J2-2041: -- Again, I am not suggesting that you

[jira] [Commented] (LOG4J2-2042) Cannot be configured for Android because of dependency on java.lang.management classes

[ https://issues.apache.org/jira/browse/LOG4J2-2042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16160900#comment-16160900 ] William Ferguson commented on LOG4J2-2042: -- NB this was when run after configuri

[jira] [Created] (LOG4J2-2042) Cannot be configured for Android because of dependency on java.lang.management classes

William Ferguson created LOG4J2-2042: Summary: Cannot be configured for Android because of dependency on java.lang.management classes Key: LOG4J2-2042 URL: https://issues.apache.org/jira/browse/LOG4J2-2042

[jira] [Commented] (LOG4J2-2041) 2.9.0 contains classes built to class version 53

[ https://issues.apache.org/jira/browse/LOG4J2-2041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16160896#comment-16160896 ] Ralph Goers commented on LOG4J2-2041: - That is impossible as they use classes only av

[jira] [Commented] (LOG4J2-2041) 2.9.0 contains classes built to class version 53

[ https://issues.apache.org/jira/browse/LOG4J2-2041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16160855#comment-16160855 ] William Ferguson commented on LOG4J2-2041: -- I never suggested the 2 classes be r

Re: Log4j support for Tomcat, TomEE, JBoss, etc.

I created a Log4J-appserver module and added the Tomcat support there. I took a look at jetty and it supports Log4J by routing it through slf4j. I'd like to change that but I am not too familiar with the internals of jetty so that might take a bit. Ralph > On Sep 7, 2017, at 4:47 AM, Mikael St

Log4J 2.9.1 release

I am thinking about doing the Log4J 2.9.1 release at the end of the week as there are a couple of bugs I'd like published by the time Java 9 is released. Ralph

[jira] [Closed] (LOG4J2-2041) 2.9.0 contains classes built to class version 53

[ https://issues.apache.org/jira/browse/LOG4J2-2041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers closed LOG4J2-2041. --- > 2.9.0 contains classes built to class version 53 > > >

[jira] [Resolved] (LOG4J2-2041) 2.9.0 contains classes built to class version 53

[ https://issues.apache.org/jira/browse/LOG4J2-2041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-2041. - Resolution: Won't Fix Log4j 2 uses a multi-release jar for log4j-api. The jar contains 2 classes

[jira] [Created] (LOG4J2-2041) 2.9.0 contains classes built to class version 53

William Ferguson created LOG4J2-2041: Summary: 2.9.0 contains classes built to class version 53 Key: LOG4J2-2041 URL: https://issues.apache.org/jira/browse/LOG4J2-2041 Project: Log4j 2 Is

[jira] [Resolved] (LOG4J2-2025) Support Tomcat JULI's per-webapp JUL logging by implementing java.util.logging.Handler

[ https://issues.apache.org/jira/browse/LOG4J2-2025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-2025. - Resolution: Fixed Fix Version/s: 2.9.1 > Support Tomcat JULI's per-webapp JUL logging by i

[jira] [Commented] (LOG4J2-2025) Support Tomcat JULI's per-webapp JUL logging by implementing java.util.logging.Handler

[ https://issues.apache.org/jira/browse/LOG4J2-2025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16160821#comment-16160821 ] Ralph Goers commented on LOG4J2-2025: - I was able to add this support using Tomcat's

[jira] [Commented] (LOG4J2-2025) Support Tomcat JULI's per-webapp JUL logging by implementing java.util.logging.Handler

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