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

I can build on my machine and the log4j-server jars are in the snapshot repo so I am not sure why this build is not finding it. Hm... this is because log4j-server is in a different module from log4j? And so looks for a non-snapshot repo only? Do we need to add the snapshot repo to the main log4j PO

Re: Left to do for 2.9 release

> On Jul 31, 2017, at 5:59, Gary Gregory wrote: > > On Sun, Jul 30, 2017 at 1:48 PM, Gary Gregory > wrote: > >> * I think the new logic to avoid logging calls blowing up ( >> ConcurrentModificationException) circumvents the ignoreExceptions >> settings on appenders. >> > > If wonder if we sh

[jira] [Commented] (LOG4J2-1990) ConcurrentModificationException logging a parameter of type Map

[ https://issues.apache.org/jira/browse/LOG4J2-1990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16106701#comment-16106701 ] Remko Popma commented on LOG4J2-1990: - The remaining problem is "where does the confi

Build failed in Jenkins: Log4j 2.x #2968

See Changes: [rpopma] LOG4J2-1990 move exception handling out of hot code path -- [...truncated 950.79 KB...] at org.junit.internal.runners.model.ReflectiveCal

Build failed in Jenkins: Log4j 2.x #2967

See Changes: [ggregory] Revert "[LOG4J2-1990] ConcurrentModificationException logging a -- [...truncated 953.91 KB...] at org.junit.runners.model.FrameworkMeth

[jira] [Commented] (LOG4J2-1990) ConcurrentModificationException logging a parameter of type Map

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

[jira] [Commented] (LOG4J2-1990) ConcurrentModificationException logging a parameter of type Map

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

Build failed in Jenkins: Log4j 2.x #2966

See Changes: [ggregory] Move some classes around to avoid a dependency cycle now that the JMS [ggregory] [LOG4J2-1990] ConcurrentModificationException logging a parameter of -

Re: Left to do for 2.9 release

I just pushed an update that fixes the currently failing tests for JMS and Flume. Gary On Sun, Jul 30, 2017 at 1:59 PM, Gary Gregory wrote: > On Sun, Jul 30, 2017 at 1:48 PM, Gary Gregory > wrote: > >> * I think the new logic to avoid logging calls blowing up >> (ConcurrentModificationExceptio

Jenkins build is still unstable: Log4j 2.x #2965

See

[jira] [Commented] (LOG4J2-1990) ConcurrentModificationException logging a parameter of type Map

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

Re: Left to do for 2.9 release

On Sun, Jul 30, 2017 at 1:48 PM, Gary Gregory wrote: > * I think the new logic to avoid logging calls blowing up ( > ConcurrentModificationException) circumvents the ignoreExceptions > settings on appenders. > If wonder if we should change the org.apache.logging.log4j.spi.AbstractLogger.tryLogMe

Re: Left to do for 2.9 release

* I think the new logic to avoid logging calls blowing up (ConcurrentModificationException) circumvents the ignoreExceptions settings on appenders. * "Fix broken JmsServer in log4j-server": I'm not that but that's how I discovered the above. * "Prepare release of logging-log4j-tools repo (if we w

[jira] [Commented] (LOG4J2-1990) ConcurrentModificationException logging a parameter of type Map

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

Re: Left to do for 2.9 release

Provided I find time this week, I'd like to merge in the properties simplification stuff I mentioned a little while ago. On 30 July 2017 at 14:51, Mikael Ståldal wrote: > * Ensure that Scala API documentation will be present on Log4j website. > > * Fix broken JmsServer in log4j-server. > > * Pre

Re: [ANN] Log4j Scala API version 11.0 is now released

I have made sure that this will end up on Scaladex (index.scala-lang.org): https://github.com/scalacenter/scaladex-contrib/pull/25 (Still waiting for it to propagate.) On 2017-07-30 03:41, Matt Sicker wrote: The PMC of the Logging Services project has released the first standalone version of

Left to do for 2.9 release

* Ensure that Scala API documentation will be present on Log4j website. * Fix broken JmsServer in log4j-server. * Prepare release of logging-log4j-tools repo (if we want to do that). Anything else?

[GitHub] logging-log4j-scala pull request #1: (Doc) Correct sbt usage

Github user asfgit closed the pull request at: https://github.com/apache/logging-log4j-scala/pull/1 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feat

Jenkins build is still unstable: Log4j 2.x #2964

See

Jenkins build is still unstable: Log4j 2.x #2963

See

Jenkins build is still unstable: Log4j 2.x #2962

See

Jenkins build is still unstable: Log4j 2.x #2961

See

Re: [log4j] Scala transition

We still need to add a link to the 2.12 component on the main site. I haven't committed the site yet as I wasn't really sure on how to support it properly, though I'm thinking it shouldn't be difficult. On 30 July 2017 at 05:23, Mikael Ståldal wrote: > I have removed the Scala code from the main

Re: log4-server JmsServer is broken

I'll take a look... On Jul 30, 2017 06:07, "Mikael Ståldal" wrote: > The JmsServer in log4j-server is currently broken, since the JmsManager in > log4j-core has changed. > > Someone needs to fix this, and I don't really know how. Gary? >

[GitHub] logging-log4j-scala pull request #1: (Doc) Correct sbt usage

GitHub user MasseGuillaume opened a pull request: https://github.com/apache/logging-log4j-scala/pull/1 (Doc) Correct sbt usage You can merge this pull request into a Git repository by running: $ git pull https://github.com/MasseGuillaume/logging-log4j-scala patch-1 Alternativ

log4-server JmsServer is broken

The JmsServer in log4j-server is currently broken, since the JmsManager in log4j-core has changed. Someone needs to fix this, and I don't really know how. Gary?

Jenkins build is still unstable: Log4j 2.x #2960

See

Jenkins build is still unstable: Log4j 2.x #2959

See

[jira] [Commented] (LOG4J2-1990) ConcurrentModificationException logging a parameter of type Map

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

Re: [log4j] Scala transition

I have removed the Scala code from the main repo now. I did not remove the documentation for it in src/site though, since it's unclear how to handle that. I updated it to reflect that we now support Scala 2.12. On 2017-07-30 03:58, Gary Gregory wrote: Hi All, Now that the log4j-scala 11.0

[jira] [Commented] (LOG4J2-1990) ConcurrentModificationException logging a parameter of type Map

[ https://issues.apache.org/jira/browse/LOG4J2-1990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16106417#comment-16106417 ] Remko Popma commented on LOG4J2-1990: - Thanks for the quick work, Gary! You're on a r