[VOTE] Release Log4j Scala API 11.1-rc1

2018-04-09 Thread Matt Sicker
Hello all, this is a vote to release 11.1 rc1 of Log4j Scala API. This release is the first release being done using sbt instead of maven. This is also the first release that supports Scala 2.13.0-M3 for early testers. This vote will remain open for at least 72 hours and requires at least 3 +1s

Re: Github PR 163

2018-04-09 Thread Carter Kozak
If my understanding of the PR is correct, I've implemented similar output using PatternLayout with a pattern along these lines, though it's not very pretty to read: {"timestamp":"%d{ISO8601}", "level":"%p", "logger":"%encode{%c}{JSON}", "thread":"%encode{%t}{JSON}", "message":

Re: Github PR 163

2018-04-09 Thread Matt Sicker
We use Jira to track features, bugs, everything really. Choose "New Feature" as the type when reporting. As for the PR being useful, I haven't looked super closely, but I could see this being potentially useful in a logging flow where a developer batches up multiple log messages to send to a

Github PR 163

2018-04-09 Thread David Knapp
I just opened up PR 163 https://github.com/apache/logging-log4j2/pull/163 It adds a new layout that's designed for key/value usage. I looked at the contributer guidelines, and they say to open a JIRA ticket, but it sort of implies that that's for bugs, not new features. Do you guys need a JIRA