Re: Java Modules

2017-10-16 Thread Ralph Goers
Just to capture this, the way this can be handled is to use the —add-exports option of javac. (See https://docs.oracle.com/javase/9/tools/javac.htm#GUID-AEEC9F07-CB49-4E96-8BC7-BCC2C7F725C9__NONSTANDARDOPTIONSFORJAVAC-7D3DAA9D

Re: Planning out what we can do to get Chainsaw back in the game

2017-10-16 Thread Matt Sicker
On 16 October 2017 at 16:11, Scott Deboy wrote: > FYI, I think most folks just use pattern layout, which probably makes > VFSLogFilePatternReceiver the most commonly used receiver. Since it's > VFS, anything accessible over SSH is retrievable and can be > live-tailed. > That would make sense si

Re: Planning out what we can do to get Chainsaw back in the game

2017-10-16 Thread Scott Deboy
FYI, I think most folks just use pattern layout, which probably makes VFSLogFilePatternReceiver the most commonly used receiver. Since it's VFS, anything accessible over SSH is retrievable and can be live-tailed. Also, Chainsaw V2 can pull in logs generated by Log4j2 if you configure an Advertise

Re: Jenkins build is still unstable: Log4j 2.x #3128

2017-10-16 Thread Matt Sicker
This looks like it goes back to before your recent commits. There were some test failure notifications earlier. On 16 October 2017 at 15:02, Mikael Ståldal wrote: > I don't understand why these tests fail: > > org.apache.logging.log4j.core.appender.db.AbstractDatabaseManagerTest.testBuffering02

Re: Planning out what we can do to get Chainsaw back in the game

2017-10-16 Thread Matt Sicker
On 16 October 2017 at 14:19, Mikael Ståldal wrote: > I think that adding support for Log4j 2's JsonLayout should be top > priority when we have figured out how to build, release and distribute it. > It should be fairly easy since we can use the new JsonLogEventParser in > log4j-core. > Agreed. M

Re: Jenkins build is still unstable: Log4j 2.x #3128

2017-10-16 Thread Mikael Ståldal
I don't understand why these tests fail: org.apache.logging.log4j.core.appender.db.AbstractDatabaseManagerTest.testBuffering02 org.apache.logging.log4j.core.appender.db.AbstractDatabaseManagerTest.testBuffering03 org.apache.logging.log4j.core.appender.db.AbstractDatabaseManagerTest.testBuffer

Re: Planning out what we can do to get Chainsaw back in the game

2017-10-16 Thread Mikael Ståldal
On 2017-10-14 20:01, Matt Sicker wrote: I have other ideas I'd like to see such as adding support for the JSON layout and future binary layouts (e.g., Avro/Thrift/Protobuf/custom binary logging format) so there is no reliance on serialized log events or dealing with ambiguous log files. I thin

Re: [Log4j] Next release?

2017-10-16 Thread Ralph Goers
I wouldn’t call myself an “expert”… but I will look at this. Ralph > On Oct 16, 2017, at 12:00 PM, Mikael Ståldal wrote: > > On 2017-10-12 21:36, Mikael Ståldal wrote: >> - https://issues.apache.org/jira/browse/LOG4J2-2062 (waiting for contributor >> to update his PR, will do it myself soon if

Re: [Log4j] Next release?

2017-10-16 Thread Mikael Ståldal
On 2017-10-12 21:36, Mikael Ståldal wrote: - https://issues.apache.org/jira/browse/LOG4J2-2062 (waiting for contributor to update his PR, will do it myself soon if he doesn't respond timey) Done. - https://issues.apache.org/jira/browse/LOG4J2-2069 (looks quite serious if it is valid) Maybe

Re: Logging list for emails generated by tools

2017-10-16 Thread Ralph Goers
All Jira, Jenkins and GitHub notifications should now be going to notificati...@logging.apache.org . Please subscribe and adjust your email setup. Ralph > On Oct 16, 2017, at 7:23 AM, Gary Gregory wrote: > > So mailto:notifications-subscr...@logging.ap

[jira] [Commented] (LOG4J2-2072) Support TLS configuration through FlumeAppender

2017-10-16 Thread Matt Sicker (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16205995#comment-16205995 ] Matt Sicker commented on LOG4J2-2072: - Info about builders: https://logging.apache.o

[jira] [Comment Edited] (LOG4J2-2072) Support TLS configuration through FlumeAppender

2017-10-16 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16205976#comment-16205976 ] Gary Gregory edited comment on LOG4J2-2072 at 10/16/17 2:29 PM: ---

[jira] [Commented] (LOG4J2-2072) Support TLS configuration through FlumeAppender

2017-10-16 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16205976#comment-16205976 ] Gary Gregory commented on LOG4J2-2072: -- IMO, the first task in this ticket should be

Re: Logging list for emails generated by tools

2017-10-16 Thread Gary Gregory
So mailto:notifications-subscr...@logging.apache.org to subscribe... Gary On Mon, Oct 16, 2017 at 7:53 AM, Ralph Goers wrote: > The mailing list notificati...@logging.apache.org notificati...@logging.apache.org> has been created. All committers should > subscribe. > > Ralph > > > On Oct 15, 20

[jira] [Commented] (LOG4J2-2072) Support TLS configuration through FlumeAppender

2017-10-16 Thread Frank Swanson (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16205951#comment-16205951 ] Frank Swanson commented on LOG4J2-2072: --- Matt, Thanks a lot for the link I think a

Re: Logging list for emails generated by tools

2017-10-16 Thread Ralph Goers
The mailing list notificati...@logging.apache.org has been created. All committers should subscribe. Ralph > On Oct 15, 2017, at 3:22 PM, Ralph Goers wrote: > > It seems there is a self-service tool to create the mailing list. > > Ralph > >> On Oct

[jira] [Commented] (LOGCXX-493) Documentation claiming `getTimeStamp` is in milliseconds but actually is in microseconds

2017-10-16 Thread Vincent Thiery (JIRA)
[ https://issues.apache.org/jira/browse/LOGCXX-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16205886#comment-16205886 ] Vincent Thiery commented on LOGCXX-493: --- Awesome! Thanks > Documentation claiming `

[GitHub] logging-log4j2 pull request #118: (doc) Fix typo in warning message

2017-10-16 Thread TimvdLippe
GitHub user TimvdLippe opened a pull request: https://github.com/apache/logging-log4j2/pull/118 (doc) Fix typo in warning message Small typo in the word "Please". You can merge this pull request into a Git repository by running: $ git pull https://github.com/TimvdLippe/logging-

[jira] [Resolved] (LOGCXX-361) 15-16 milliseconds granularity on Windows‏

2017-10-16 Thread JIRA
[ https://issues.apache.org/jira/browse/LOGCXX-361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thorsten Schöning resolved LOGCXX-361. -- Resolution: Not A Problem log4cxx uses apr_time_now which provides microseconds on suppo

[jira] [Resolved] (LOGCXX-493) Documentation claiming `getTimeStamp` is in milliseconds but actually is in microseconds

2017-10-16 Thread JIRA
[ https://issues.apache.org/jira/browse/LOGCXX-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thorsten Schöning resolved LOGCXX-493. -- Resolution: Fixed Thanks for the report, I fixed this in master and latest_stable-branch

[jira] [Updated] (LOGCXX-493) Documentation claiming `getTimeStamp` is in milliseconds but actually is in microseconds

2017-10-16 Thread JIRA
[ https://issues.apache.org/jira/browse/LOGCXX-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thorsten Schöning updated LOGCXX-493: - Fix Version/s: 0.11.0 > Documentation claiming `getTimeStamp` is in milliseconds but actua

[jira] [Assigned] (LOGCXX-493) Documentation claiming `getTimeStamp` is in milliseconds but actually is in microseconds

2017-10-16 Thread JIRA
[ https://issues.apache.org/jira/browse/LOGCXX-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thorsten Schöning reassigned LOGCXX-493: Assignee: Thorsten Schöning > Documentation claiming `getTimeStamp` is in milliseco

[jira] [Updated] (LOGCXX-493) Documentation claiming `getTimeStamp` is in milliseconds but actually is in microseconds

2017-10-16 Thread Vincent Thiery (JIRA)
[ https://issues.apache.org/jira/browse/LOGCXX-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Thiery updated LOGCXX-493: -- Summary: Documentation claiming `getTimeStamp` is in milliseconds but actually is in microsecond

[jira] [Created] (LOGCXX-493) Documentation claiming `getTimeStamp` is in milliseconds but really is in microseconds

2017-10-16 Thread Vincent Thiery (JIRA)
Vincent Thiery created LOGCXX-493: - Summary: Documentation claiming `getTimeStamp` is in milliseconds but really is in microseconds Key: LOGCXX-493 URL: https://issues.apache.org/jira/browse/LOGCXX-493