Re: Releasing 2.9

On Fri, Jul 7, 2017 at 11:06 PM, Ralph Goers wrote: > Another thing I would like to see, provided Remko or someone else has > time, is to update the performance page on the web site to reflect current > versions. I believe Logback has made some improvements and I would like to > incorporate those

Releasing 2.9

Another thing I would like to see, provided Remko or someone else has time, is to update the performance page on the web site to reflect current versions. I believe Logback has made some improvements and I would like to incorporate those. Tinylog has also asked us to include benchmarks. If the M

[jira] [Commented] (LOG4J2-928) Lock-free synchronous sub-microsecond appender

[ https://issues.apache.org/jira/browse/LOG4J2-928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16078967#comment-16078967 ] ASF GitHub Bot commented on LOG4J2-928: --- Github user remkop commented on the issue:

[GitHub] logging-log4j2 issue #87: [LOG4J2-928] Mostly wait-free MemoryMappedFileMana...

Github user remkop commented on the issue: https://github.com/apache/logging-log4j2/pull/87 @leventov The log4j community is discussing releasing a 2.9 version soon (in July). I would like to merge your contribution but have you had a chance to look at the [ICLA](http://www.apache.org

[jira] [Closed] (LOG4J2-1970) Upgrade HdrHistogram from 2.1.8 to 2.1.9

[ https://issues.apache.org/jira/browse/LOG4J2-1970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma closed LOG4J2-1970. --- Resolution: Fixed Assignee: Remko Popma > Upgrade HdrHistogram from 2.1.8 to 2.1.9 > --

[jira] [Commented] (LOG4J2-1883) Timestamp does not seem to support microseconds level

[ https://issues.apache.org/jira/browse/LOG4J2-1883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16078961#comment-16078961 ] Ralph Goers commented on LOG4J2-1883: - I looked at the code and it seems to require J

[jira] [Created] (LOG4J2-1970) Upgrade HdrHistogram from 2.1.8 to 2.1.9

Remko Popma created LOG4J2-1970: --- Summary: Upgrade HdrHistogram from 2.1.8 to 2.1.9 Key: LOG4J2-1970 URL: https://issues.apache.org/jira/browse/LOG4J2-1970 Project: Log4j 2 Issue Type: Task

Re: [Log4j] release 2.9 - Scala API

I won't be able to help out with that until next week at the earliest. I'm preparing a presentation this weekend (coincidentally one about Scala actually), but things are starting to simmer down finally. On 7 July 2017 at 13:39, Mikael Ståldal wrote: > It would be good if you could finalize the

[jira] [Commented] (LOG4J2-1883) Timestamp does not seem to support microseconds level

[ https://issues.apache.org/jira/browse/LOG4J2-1883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16078910#comment-16078910 ] Gary Gregory commented on LOG4J2-1883: -- Any community feedback for [~Anthony Maire]?

[jira] [Commented] (LOG4J2-1192) Dynamic Subject for SMTP Appender

[ https://issues.apache.org/jira/browse/LOG4J2-1192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16078908#comment-16078908 ] Gary Gregory commented on LOG4J2-1192: -- Is anyone available to submit a PR to incorp

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

This was an error related to running git, though. I guess the "wip" in the git URL really does stand for "work in progress"! ;) On 7 July 2017 at 16:58, Gary Gregory wrote: > FWIW, building on Java 8 should help... > > Gary > > On Fri, Jul 7, 2017 at 2:57 PM, Gary Gregory > wrote: > > > There s

[GitHub] logging-log4j2 issue #47: Add tinylog benchmarks

Github user jvz commented on the issue: https://github.com/apache/logging-log4j2/pull/47 Might need to add one. Should probably fall under a documentation bug type. --- 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

Re: [2/5] logging-log4j2 git commit: LOG4J2-1923 Maintain binary compatibility

You can remove the annotations on the deprecated factories. They won't be scanned when a builder class is present. On 7 July 2017 at 15:43, wrote: > LOG4J2-1923 Maintain binary compatibility > > > Project: http://git-wip-us.apache.org/repos/asf/logging-log4j2/repo > Commit: http://git-wip-us.apa

Re: [2/5] logging-log4j2 git commit: LOG4J2-1923 Maintain binary compatibility

It's also misleading ;-) Gary On Fri, Jul 7, 2017 at 7:15 PM, Matt Sicker wrote: > You can remove the annotations on the deprecated factories. They won't be > scanned when a builder class is present. > > On 7 July 2017 at 15:43, wrote: > > > LOG4J2-1923 Maintain binary compatibility > > > > >

Re: [log4cxx] Release process releated questions

>From what I remember, when I tried this before I had a problem building with ant because of dependencies, which is I think what it's using now for release. PR#2 on Github fixes this to just use shell executions with Maven, although if it's working for you currently then I don't see a need to chan

Re: [log4cxx] Release process releated questions

That is a great suggestion! Ralph > On Jul 7, 2017, at 1:51 PM, Gary Gregory wrote: > > You might want to clone the Log4j 2 build wiki and replace the Git and Java > parts with your build system and language specific parts. > > Gary > > On Fri, Jul 7, 2017 at 1:41 PM, Matt Sicker wrote: > >

[jira] [Commented] (LOG4J2-1933) Not able to init config with JsonConfiguration class while the json config nodes are in random order

[ https://issues.apache.org/jira/browse/LOG4J2-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16078803#comment-16078803 ] Gary Gregory commented on LOG4J2-1933: -- I think we should not spend more time on thi

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

See

[jira] [Commented] (LOG4J2-1933) Not able to init config with JsonConfiguration class while the json config nodes are in random order

[ https://issues.apache.org/jira/browse/LOG4J2-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16078794#comment-16078794 ] Ralph Goers commented on LOG4J2-1933: - Although json.org says an object is an unorder

Build failed in Jenkins: Log4j 2.x #2878

See -- [...truncated 4.25 KB...] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:748) at ..r

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

FWIW, building on Java 8 should help... Gary On Fri, Jul 7, 2017 at 2:57 PM, Gary Gregory wrote: > There seems to be a problem with Jenkins on a daily bases. PITA. Just > frustrated... > > Gary > > -- Forwarded message -- > From: Apache Jenkins Server > Date: Fri, Jul 7, 2017 a

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

There seems to be a problem with Jenkins on a daily bases. PITA. Just frustrated... Gary -- Forwarded message -- From: Apache Jenkins Server Date: Fri, Jul 7, 2017 at 2:55 PM Subject: Build failed in Jenkins: Log4j 2.x #2877 To: dev@logging.apache.org See

[jira] [Comment Edited] (LOG4J2-1934) JMS Appender does not know how to recover from a broken connection

[ https://issues.apache.org/jira/browse/LOG4J2-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16078757#comment-16078757 ] Gary Gregory edited comment on LOG4J2-1934 at 7/7/17 9:56 PM: -

[jira] [Commented] (LOG4J2-1955) JMS Appender should be able connect to a broker (later) even it is not present at configuration time

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

[jira] [Commented] (LOG4J2-1934) JMS Appender does not know how to recover from a broken connection

[ https://issues.apache.org/jira/browse/LOG4J2-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16078757#comment-16078757 ] Gary Gregory commented on LOG4J2-1934: -- Add added a "Default" column to the table fo

[jira] [Commented] (LOG4J2-1934) JMS Appender does not know how to recover from a broken connection

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

Build failed in Jenkins: Log4j 2.x #2877

See -- [...truncated 3.99 KB...] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:748) at ..r

[jira] [Commented] (LOG4J2-1511) DynamicThresholdFilter filters incorrectly when params are passed as individual arguments instead of varargs

[ https://issues.apache.org/jira/browse/LOG4J2-1511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16078713#comment-16078713 ] ASF GitHub Bot commented on LOG4J2-1511: Github user garydgregory commented on th

[GitHub] logging-log4j2 issue #40: LOG4J2-1511-fix-dynamic-threshold-filter-to-work-w...

Github user garydgregory commented on the issue: https://github.com/apache/logging-log4j2/pull/40 @surukuntu : Would you be so kind as to verify and close if master is up to snuff? I think this was covered by commit 0c9c9f384475af3402833e9a2a27e97248b84b38: ``` co

[GitHub] logging-log4j2 issue #82: Add a new LuceneAppender which writes logging even...

Github user garydgregory commented on the issue: https://github.com/apache/logging-log4j2/pull/82 Note that the idea with the "5" naming is to have both modules log4j-lucene5 now and later log4j-lucene6 Gary --- If your project is set up for it, you can reply to this email a

[GitHub] logging-log4j2 issue #82: Add a new LuceneAppender which writes logging even...

Github user garydgregory commented on the issue: https://github.com/apache/logging-log4j2/pull/82 Hi, I can't recall if we have one but I brought in the code locally and started fiddling with it. Please see the Lucene 5 branch here: https://git-wip-us.apache.o

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

See

[jira] [Commented] (LOG4J2-1301) Automatic reconfiguration with xml and xinclude

[ https://issues.apache.org/jira/browse/LOG4J2-1301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16078678#comment-16078678 ] ASF GitHub Bot commented on LOG4J2-1301: Github user mikaelstaldal commented on t

[GitHub] logging-log4j2 issue #25: LOG4J2-1301 added optionalMonitorFiles attribute f...

Github user mikaelstaldal commented on the issue: https://github.com/apache/logging-log4j2/pull/25 Linking: https://issues.apache.org/jira/browse/LOG4J2-1301 --- 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

[GitHub] logging-log4j2 issue #40: LOG4J2-1511-fix-dynamic-threshold-filter-to-work-w...

Github user mikaelstaldal commented on the issue: https://github.com/apache/logging-log4j2/pull/40 Can this PR be closed @garydgregory ? --- 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 f

[jira] [Commented] (LOG4J2-1511) DynamicThresholdFilter filters incorrectly when params are passed as individual arguments instead of varargs

[ https://issues.apache.org/jira/browse/LOG4J2-1511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16078675#comment-16078675 ] ASF GitHub Bot commented on LOG4J2-1511: Github user mikaelstaldal commented on t

Re: [1/5] logging-log4j2 git commit: LOG4J2-1923 Allow having the stacktrace as a string in JSONLayout, XMLLayout and YAMLLayout

Nit: "stacktraceAsString" -> "stacktTaceAsString". On Fri, Jul 7, 2017 at 1:43 PM, wrote: > Repository: logging-log4j2 > Updated Branches: > refs/heads/master 96eb72e3c -> c016e8978 > > > LOG4J2-1923 Allow having the stacktrace as a string in JSONLayout, > XMLLayout and YAMLLayout > > > Projec

Re: [log4cxx] Release process releated questions

You might want to clone the Log4j 2 build wiki and replace the Git and Java parts with your build system and language specific parts. Gary On Fri, Jul 7, 2017 at 1:41 PM, Matt Sicker wrote: > 1. You should add it to the logging project's KEYS file. I think I was one > of the last keys added to

[GitHub] logging-log4j2 issue #47: Add tinylog benchmarks

Github user mikaelstaldal commented on the issue: https://github.com/apache/logging-log4j2/pull/47 Which JIRA issue is this? --- 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 enabl

[GitHub] logging-log4j2 issue #59: Fix rollover to work when filePattern contains no ...

Github user mikaelstaldal commented on the issue: https://github.com/apache/logging-log4j2/pull/59 Can this PR be closed? --- 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

[GitHub] logging-log4j2 issue #82: Add a new LuceneAppender which writes logging even...

Github user mikaelstaldal commented on the issue: https://github.com/apache/logging-log4j2/pull/82 Which JIRA issue is this? --- 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 enabl

Re: [Log4j] release 2.9

Done. On 2017-07-05 21:15, Mikael Ståldal wrote: There are a couple of almost finished PRs on GitHub which would be nice to include. I'll have a look at LOG4J2-1923 (PR #81) in the comming days.

[jira] [Resolved] (LOG4J2-1923) JSONLayout should allow stacktrace as string

[ https://issues.apache.org/jira/browse/LOG4J2-1923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal resolved LOG4J2-1923. Resolution: Fixed Fix Version/s: 2.9 In Git master, please verify and close. > JSON

[jira] [Commented] (LOG4J2-1923) JSONLayout should allow stacktrace as string

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

[jira] [Commented] (LOG4J2-1923) JSONLayout should allow stacktrace as string

[ https://issues.apache.org/jira/browse/LOG4J2-1923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16078659#comment-16078659 ] ASF GitHub Bot commented on LOG4J2-1923: Github user asfgit closed the pull reque

[GitHub] logging-log4j2 pull request #81: [LOG4J2-1923] Allow having the stacktrace a...

Github user asfgit closed the pull request at: https://github.com/apache/logging-log4j2/pull/81 --- 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 feature

Re: [log4cxx] Release process releated questions

1. You should add it to the logging project's KEYS file. I think I was one of the last keys added to the file. 2. I don't know of any C++ projects distributed through Maven Central. There are projects written mostly in C or C++ that bind to Java which are on MC, though. 3. I'm not exactly sure on

Jenkins build is unstable: Log4j 2.x #2875

See

[log4cxx] Release process releated questions

Hi all, I'm working on a release for log4cxx and have some questions about the process itself: 1. KEYS in dist-repo There's a KEYS file at the root of our dist-repo, do I need to get added there with my signing key? I've added it wherever the docs told me, KEYS in project repo, home.apache.org,

Re: logging-log4j2 git commit: LOG4J2-1934 Fix typo

Thank you Mike! Gary On Jul 7, 2017 12:16, wrote: > Repository: logging-log4j2 > Updated Branches: > refs/heads/master 9fc8b7651 -> 96eb72e3c > > > LOG4J2-1934 Fix typo > > > Project: http://git-wip-us.apache.org/repos/asf/logging-log4j2/repo > Commit: http://git-wip-us.apache.org/repos/asf/l

Build failed in Jenkins: Log4j 2.x #2874

See -- [...truncated 3.99 KB...] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:748) at ..r

[jira] [Commented] (LOG4J2-1969) TcpSocketServer does not replace any “{}” in message

[ https://issues.apache.org/jira/browse/LOG4J2-1969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16078544#comment-16078544 ] Mikael Ståldal commented on LOG4J2-1969: Could you try this with the latest versi

[jira] [Commented] (LOG4J2-1934) JMS Appender does not know how to recover from a broken connection

[ https://issues.apache.org/jira/browse/LOG4J2-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16078535#comment-16078535 ] Mikael Ståldal commented on LOG4J2-1934: I think the comment on JmsManager.Reconn

[jira] [Commented] (LOG4J2-1934) JMS Appender does not know how to recover from a broken connection

[ https://issues.apache.org/jira/browse/LOG4J2-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16078526#comment-16078526 ] Mikael Ståldal commented on LOG4J2-1934: The documentation should mention the def

[jira] [Commented] (LOG4J2-1933) Not able to init config with JsonConfiguration class while the json config nodes are in random order

[ https://issues.apache.org/jira/browse/LOG4J2-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16078521#comment-16078521 ] ASF GitHub Bot commented on LOG4J2-1933: Github user mikaelstaldal commented on t

[GitHub] logging-log4j2 issue #91: failing test - irregular log4j2.json nodes order

Github user mikaelstaldal commented on the issue: https://github.com/apache/logging-log4j2/pull/91 For https://issues.apache.org/jira/browse/LOG4J2-1933 --- 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

Re: [Log4j] release 2.9 - Scala API

It would be good if you could finalize the release of logging-log4j-scala. I am ready to help. On 2017-07-07 01:04, Matt Sicker wrote: The code as is should be ready for source and binary artifacts I believe. I don't recall if there was a distribution zip task already set up, though, and I beli