Re: @Log annotation

On Thu, Jul 19, 2018 at 8:07 AM Rob Tompkins wrote: > > > > On Jul 19, 2018, at 9:29 AM, Gary Gregory > wrote: > > > > Annotation-based logging comes up once in a while here but we have not > > implemented it. Project Lombok does that IIRC. > > Any reaso

Re: @Log annotation

Annotation-based logging comes up once in a while here but we have not implemented it. Project Lombok does that IIRC. Gary On Thu, Jul 19, 2018, 07:15 Rob Tompkins wrote: > Hey folks, > > I’m curious if anyone has thought about adding a class level @Log > annotation such that upon debug or trac

Re: logging-log4j2 git commit: Revert "Inline private StringBuilders.escapeAndDecrement"

Thank you Carter. Gary On Mon, Jul 16, 2018 at 8:47 AM wrote: > Repository: logging-log4j2 > Updated Branches: > refs/heads/master ac0bf4bbe -> 424e6a0fe > > > Revert "Inline private StringBuilders.escapeAndDecrement" > > This reverts commit ac0bf4bbe85cd4a07af195b3b001717a72888794. > > > Pr

Re: logging-log4j2 git commit: Inline private StringBuilders.escapeAndDecrement

I am -1 to this and this kind of change. Please revert. The JVM will in-line small methods for you. We have actually had work in the other direction: Making sure heavily used methods a tiny so that the JVM will in-line them. I think the limit is.. 35 bytes? Gary On Mon, Jul 16, 2018 at 8:39 AM

Re: [Log4j2] RollingFileAppender ignores immediateFlush

we don’t support file locking on the RollingFileManager. > > Ralph > > > On Jul 14, 2018, at 9:40 AM, Gary Gregory > wrote: > > > > On Sat, Jul 14, 2018 at 9:13 AM Gary Gregory > wrote: > > > >> > >> > >> On Fri, Jul 13, 2018 at 7

Re: [Log4j2] RollingFileAppender ignores immediateFlush

On Sat, Jul 14, 2018 at 9:13 AM Gary Gregory wrote: > > > On Fri, Jul 13, 2018 at 7:53 PM Remko Popma wrote: > >> >> > On Jul 14, 2018, at 10:49, Remko Popma wrote: >> > >> > Be careful in this area. I remember this was quite tricky! >> > &

Re: [Log4j2] RollingFileAppender ignores immediateFlush

needs careful inspection which I will do. I had a RollingFileAppender that was not behaving as I expected and that's when I debugged the code and noticed that immeditateFlush was not passed along. Gary > > > > > Remko > > > >>> On Jul 14, 2018, at 9: 27, Gary Gregory >

Re: log4j-core.jar size

In git master for 3.0.0-SNAPSHOT we have moved code from core to new modules. Gary On Sat, Jul 14, 2018, 03:16 Mark Struberg wrote: > hi folks! > > I've noticed that log4j-core.jar is now 1.6MB in size. That used to be > 600kB in 2.0 and 300kB in log4j-1.2.9. > > This sounds like there might be

Re: [Log4j2] RollingFileAppender ignores immediateFlush

On Fri, Jul 13, 2018 at 6:22 PM Gary Gregory wrote: > Hi All: > > Looks like a bug and not by design in: > > org.apache.logging.log4j.core.appender.rolling.RollingFileManager.RollingFileManager(LoggerContext, > String, String, OutputStream, boolean, boolean, long, long,

[Log4j2] RollingFileAppender ignores immediateFlush

Hi All: Looks like a bug and not by design in: org.apache.logging.log4j.core.appender.rolling.RollingFileManager.RollingFileManager(LoggerContext, String, String, OutputStream, boolean, boolean, long, long, TriggeringPolicy, RolloverStrategy, String, Layout, String, String, String, boolean, ByteB

Self documenting Loggers

At work, we have tons of loggers, mostly based on class names, with also some general purpose loggers. We have had different UIs over the years to deal with configuration but one thing we have never had is the description of what a logger does. What do you think of being able to say things like:

Re: [VOTE] Release Log4j Kotlin API 1.0.0-rc1

Sorry, I mean just sha files are missing. On Mon, Jul 9, 2018 at 1:44 PM Gary Gregory wrote: > Hi Matt, > > You are missing asc and sha256 files from > https://dist.apache.org/repos/dist/dev/logging/log4j/kotlin/ > > Gary > > On Sat, Jul 7, 2018 at 1:11 PM Matt Sicker

Re: [VOTE] Release Log4j Kotlin API 1.0.0-rc1

Hi Matt, You are missing asc and sha256 files from https://dist.apache.org/repos/dist/dev/logging/log4j/kotlin/ Gary On Sat, Jul 7, 2018 at 1:11 PM Matt Sicker wrote: > Hi all, we have a brand new Log4j API to release, and this is the first > release candidate to work with. Below are links to

Re: Log4j 2.11.1

Good news! Gary On Wed, Jun 27, 2018 at 11:17 AM Ralph Goers wrote: > I should have some time this weekend to perform a release of Log4j 2.11.1. > Just letting you all know in case there is more you would like to get done. > > We should also consider when a 3.0.0 release should be done. I’d lik

Re: StatusLogger contention?

So any thoughts on how the output got garbled in a Maven build? I wonder if Maven 3.5.4 introduced a bug? Gary On Tue, Jun 26, 2018, 15:47 Ralph Goers wrote: > No. > > Ralph > > > On Jun 26, 2018, at 12:18 PM, Gary Gregory > wrote: > > > > Hi All: > &

Fwd: StatusLogger contention?

Hi All: I get this garbled StatusLogger output when running Mongo tests from Maven: [INFO] Running org.apache.logging.log4j.mongodb3.MongoDbMapMessageTest ERREERORRROOR StatusLogger No Log4j 2 configuration file founRd. UsingR defau StatusLogger No Log4j 2 configuration file found.lt configuratio

Re: [VOTE] Migrate git repositories to gitbox

t;>>>>>> On Apr 29, 2018, at 7:38 PM, Ílson Bolzan > > >>> wrote: > > >>>>>>> +1 > > >>>>>>> > > >>>>>>>> On Sun, Apr 29, 2018 at 3:20 PM, Matt Sicker > > &g

Re: Reminder - [VOTE] Release Log4j Audit 1.0.0 RC1

ime I really wouldn’t > like to have the software just languish. > > The bottom line is you should use whatever criteria makes YOU comfortable, > not me. > > Ralph > > > On Jun 15, 2018, at 4:29 PM, Gary Gregory > wrote: > > > > Ralph, > > > > I

Re: Reminder - [VOTE] Release Log4j Audit 1.0.0 RC1

ere I have computers set up for testing > Apache > >> releases. > >> > >> On 12 June 2018 at 22:10, Remko Popma wrote: > >> > >>> +1 > >>> > >>> (Shameless plug) Every java main() method deserves http://picocli.info >

Re: Reminder - [VOTE] Release Log4j Audit 1.0.0 RC1

> >> +1 > >> > >> (Shameless plug) Every java main() method deserves http://picocli.info > >> > >>> On Jun 13, 2018, at 9:03, Gary Gregory wrote: > >>> > >>> I started reading the site, which is good so far... should be able

Re: logging-log4j2 git commit: [LOG4J2-2351] Added AbstractLogEvent.getMutableInstant

Hi, The semantics are quite different now, right? Before, the instant ivar was initialized on object instantiation, 'my instant is when I was created.' Now, it's value is a random amount of time after instantiation. How can that be right? Gary On Wed, Jun 13, 2018 at 6:14 AM wrote: > Repositor

Re: Reminder - [VOTE] Release Log4j Audit 1.0.0 RC1

I started reading the site, which is good so far... should be able to continue tomorrow... Gary On Tue, Jun 12, 2018, 17:35 Ralph Goers wrote: > 48 hours have passed with no votes or discussion. > > Ralph > > > On Jun 10, 2018, at 2:26 PM, Ralph Goers > wrote: > > > > This is a vote to release

Re: [log4j] 2.11.1 release timeline

The earlier the better ;-) We need an RM to volunteer, that's been Ralph in the past mostly. Gary On Tue, Jun 12, 2018 at 9:26 AM Carter Kozak wrote: > Hi all, > > Do we have a release schedule for 2.11.1? I'm more than happy to > assist with the process. > > Best, > -ck >

[log4j] master unit failures

Hi All: It looks like the latest commit causes the build to fail in the log4j-1.2-api module. Gary

Re: [jira] [Closed] (LOG4J2-2337) JSONLayout printing \r at end of line

unnecessary in my opinion. > > Remko > > > On May 9, 2018, at 8:46, Gary Gregory wrote: > > > > I think that is a wrong view of how to use Jira. I imagine that people > post > > to Jira either out of ignorance, or for not wanting to subscribe to a > > ma

Re: [jira] [Closed] (LOG4J2-2337) JSONLayout printing \r at end of line

s with users, users are often not experts after all. > > Thoughts? > > Remko > > > > > On May 9, 2018, at 2:42, Gary Gregory (JIRA) wrote: > > > > > > [ > https://issues.apache.org/jira/browse/LOG4J2-2337?page=com.atlassian.jira.plug

Re: Log4j and OSGi

Even before that, or, for that, we already have a medium size change set for 2.11.1. Any thoughts on a time frame for releasing? Gary On Mon, May 7, 2018 at 2:55 PM, Ralph Goers wrote: > I just noticed https://github.com/rotty3000/osgi.to.logback < > https://github.com/rotty3000/osgi.to.logback

Re: [VOTE] Migrate git repositories to gitbox

+1 Gary On Sat, Apr 28, 2018, 17:12 Matt Sicker wrote: > This is a vote to migrate from the existing git-wip-us infrastructure to > the currently supported gitbox infrastructure that Infra advocates for > using nowadays. Using gitbox will allow our projects to integrate better > with GitHub inc

Re: LOG4J2-2327 commit veto

Done. Please see my follow up comment in the JIRA. Gary On Thu, Apr 26, 2018 at 1:25 PM, Ralph Goers wrote: > Gary, > > In case you don’t see the email from Jira I want to make sure you see that > I vetoed the code commit you did for LOG4J2-2327. The reasons for it are in > the Jira issue. > >

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

How do we fix this? Gary -- Forwarded message -- From: Apache Jenkins Server Date: Thu, Apr 26, 2018 at 11:58 AM Subject: Build failed in Jenkins: Log4j 2 2.x #3461 To: notificati...@logging.apache.org See -

Re: Interesting fluent logging API

If we are considering new APIs, I still like what I proposed a long time ago in a branch somewhere based on levels. Something like: Level.WARN.log(logger, ...) This avoids having a gazillion new method whenever we want to add a new kind of method (or a new level.) Gary On Wed, Apr 25, 2018 at 1

Re: [log4j] Curious about WatchManager implementation

On 12 April 2018 at 11:24, Remko Popma wrote: > > > I remember Ralph looked at it but concluded it wasn’t fit for purpose. I > > forget the details but it’s on the mailing list somewhere. > > > > Remko > > > > (Shameless plug) Every java main() method deserves http

[log4j] Curious about WatchManager implementation

Hi All: Our WatchManager pools on a thread to watch files. Is there any reason why we are not using Java 7's WatchService? Yes, I know it only watches folders and not files but I consider that a detail ;-) Gary

Re: [VOTE] Release Log4j Scala API 11.1-rc1

; > to deal with. > > > > Ralph > > > > > On Apr 11, 2018, at 1:29 PM, Gary Gregory > > wrote: > > > > > > The commands start with "./", you do not want that on Windows. > > > > > > Gary > > > > > &

Re: [VOTE] Release Log4j Scala API 11.1-rc1

The commands start with "./", you do not want that on Windows. Gary On Wed, Apr 11, 2018 at 2:19 PM, Ralph Goers wrote: > What instructions are you talking about? BUILDING.md? Why don’t they work > on Windows? > > Ralph > > > On Apr 11, 2018, at 12:48 PM, Gary

Re: [VOTE] Release Log4j Scala API 11.1-rc1

Also these instructions need adjustment for Windows, I'd like to cut and paste... ;-) Gary On Wed, Apr 11, 2018 at 1:46 PM, Gary Gregory wrote: > Hi Matt: > > The file BUILDING.md contains: > > Moved to [site docs](./src/asciidoctor/build.adoc). > > Summary: > >

Re: [VOTE] Release Log4j Scala API 11.1-rc1

Hi Matt: The file BUILDING.md contains: Moved to [site docs](./src/asciidoctor/build.adoc). Summary: ./sbt "+ publishM2" But build.adoc does not contain the command in your summary above. Gary On Mon, Apr 9, 2018 at 1:32 PM, Matt Sicker wrote: > Hello all, this is a vote to release 1

Re: [VOTE] Release Log4j Scala API 11.1-rc1

Matt: I looks like your key has expired: $ gpg --verify apache-log4j-api-scala-11.1-src.zip.asc gpg: assuming signed data in `apache-log4j-api-scala-11.1-src.zip' gpg: Signature made Mon, Apr 9, 2018 13:07:12 MDT using RSA key ID B62BABE8 gpg: Good signature from "Matthew Sicker (Signing Key) <

Re: [VOTE] Release Log4j Scala API 11.1-rc1

Hi Matt: We need to SHA1 files in https://dist.apache.org/repos/dist/dev/logging/log4j/scala/ Gary On Mon, Apr 9, 2018 at 1:32 PM, Matt Sicker wrote: > 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. T

Re: [log4j] com.lmax.disruptor.collections.Histogram gone in LMAX 3.4.x

eserves http://picocli.info > > > On Apr 9, 2018, at 7:12, Gary Gregory wrote: > > > > Hi All: > > > > It looks like LMAX removed com.lmax.disruptor.collections.Histogram in > the > > current 3.4.x. > > > > We will have to copy it into our test

[log4j]

When I change my log4j XML config file and I have status logging set to DEBUG, I see: 2018-04-10 13:48:43,895 Log4j2-TF-1-ConfiguratonFileWatcher-3 ERROR Could not register mbeans javax.management.InstanceAlreadyExistsException: org.apache.logging.log4j2:type=6d06d69c at com.sun.jmx.mbeanserver.Re

[log4j] com.lmax.disruptor.collections.Histogram gone in LMAX 3.4.x

Hi All: It looks like LMAX removed com.lmax.disruptor.collections.Histogram in the current 3.4.x. We will have to copy it into our test code base if we want to keep using it and keep up with LMAX versions. Gary

[log4j] Thoughts on adding log4j2.forceTCLOnly option (#140)

Any thoughts on this PR? Gary -- Forwarded message -- From: Romain Manni-Bucau Date: Tue, Jan 9, 2018 at 4:00 AM Subject: [apache/logging-log4j2] adding log4j2.forceTCLOnly option (#140) To: apache/logging-log4j2 Cc: Subscribed -- You can view, com

Re: [Log4j] Windows build failures on Jenkins

osx which may not be compatible with my environment, > > >> works on linux though) on osx, haven't had a chance to dig into them > > >> quite yet. > > >> > > >> I've executed the tests on my changes prior to committing, but may > > >

Re: [Log4j] Windows build failures on Jenkins

.java:407) [surefire-booter-2.20.1.jar:2.20.1] Caused by: java.util.zip.ZipException: archive is not a ZIP archive Clear C:\Users\jenkins\.embedmongo\ and try again? Gary > > [1]: > https://builds.apache.org/job/Log4jCore/job/master/17/ > execution/node/27/log/ > > On 7 April 2018 at

Re: [Log4j] Windows build failures on Jenkins

There was a commit today or last night, I think about messages and parameters, maybe it is related. Gary On Sat, Apr 7, 2018, 10:22 Matt Sicker wrote: > I'm actually getting the same test failures on macOS now. Might just be a > regression. > > On 7 April 2018 at 11:15, Matt Sicker wrote: > >

Re: [log4j] Better init status logger message

Done: https://issues.apache.org/jira/browse/LOG4J2-2302 Gary On Sun, Apr 1, 2018 at 12:08 PM, Matt Sicker wrote: > Makes sense to me. Debugging weird configurations should always be easier. > > On 1 April 2018 at 12:41, Gary Gregory wrote: > > > Hi All: > > > &

Re: Console performance

I'm sure this is OS dependent as well. I've only seen the obvious: if you log a ton of data, say at the DEBUG level, and enable DEBUG, then yeah, things are going to slow down. Obvious. The complain I usually hear is that our server logs too much DEBUG data, and that users do not know which log ca

[log4j] LOG4J2-2300

Hi All: I did something bad to the pooch when I created the new plugin for JDBC and Apache Commons DBCP 2. LOG4J2-2300 is fixed in the release 2.x branch and master. So if anyone has an itch to RM a release, I would be grateful. Gary

[log4j] Better init status logger message

Hi All: Instead of a status logger message like: 2018-04-01 11:39:22,615 main DEBUG Initializing configuration XmlConfiguration[location=C:\Users\ggregory\workspaces\centipede\DevTests\target\test-classes\log4j2.xml] I'd like to see: 2018-04-01 11:39:22,615 main DEBUG Log4j 2.11.0 initializing

Re: [Scala] New site preview

Looks great on Android/Firefox. Gary On Sat, Mar 31, 2018, 19:43 Matt Sicker wrote: > So I've been working on converting the build to use SBT, and part of that > means migrating the site to use a different site generator. AsciiDoc seemed > to be the way to go so far. I've uploaded a snapshot of

Re: Support for 2.x

Sounds fine to me. (Had the flu since Wednesday, just coming out of it.) Gary On Sun, Mar 18, 2018, 11:10 Ralph Goers wrote: > Although I would like to see us start doing 3.x releases I don’t think it > is time to stop supporting 2.x. To that end, where applicable I think we > should continue

Re: [VOTE] Release Log4j 2.11.0-rc1

ule to > > allow benchmarking with Java 9 APIs. > > • LOG4J2-2193: Update JMH to version 1.19 from 1.1.1. > > • LOG4J2-2132: Update ZeroMQ's jeromq from 0.4.2 to 0.4.3. > > • LOG4J2-2165: Update Jackson from 2.9.2 to 2.9.3. > > • LOG4J2-2184: Upda

Re: [VOTE] Release Log4j 2.11.0-rc1

h [null] returns > "null" instead of EMPTY. Thanks to Cyril Martin. > • LOG4J2-2276: ConcurrentModificationException from > org.apache.logging.log4j.status.StatusLogger.(StatusLogger.java:71). > Thanks to Sean Baxter. > • LOG4J2-2274: Allow EnvironmentPropertySour

Re: 2.11.0 status

; > > I can’t answer that except to say that I don’t think that will change > for 2.11.0. I have no idea why we have anything to do with the command > line in Log4j. > > > > Ralph > > > >> On Mar 11, 2018, at 11:42 AM, Gary Gregory > wrote: > >> >

Re: 2.11.0 status

80->parseInvalidValue:496 > Invalid format %$::a?*!a was accepted for -InetAddress > [INFO] > [ERROR] Tests run: 199, Failures: 1, Errors: 0, Skipped: 4 > > Ralph > > > On Mar 9, 2018, at 12:23 PM, Gary Gregory > wrote: > > > > On Thu, Mar 8, 2018 at 9:48 PM

Re: 2.11.0 status

On Thu, Mar 8, 2018 at 9:48 PM, Ralph Goers wrote: > I have created the release notes for 2.11.0. Please review them. > > I have built the 2.11.0 web site locally and am noticing the following > problems: > > The javadoc page does not list jdbc-dbc2, jpa, or liquibase. > The link on the javadco p

Re: 2.11.0 status

The main page shows "h3" in the heading text "h3 Integrating with Application Servers" I'll review some more tomorrow. Gary On Thu, Mar 8, 2018 at 9:48 PM, Ralph Goers wrote: > I have created the release notes for 2.11.0. Please review them. > > I have built the 2.11.0 web site locally and am

Re: org.apache.logging.log4j.core.layout.AbstractStringLayout.getContentType() does not use Charset

Gary > Ralph > > > On Mar 6, 2018, at 9:17 PM, Gary Gregory wrote: > > > >> On Tue, Mar 6, 2018 at 6:01 PM, Remko Popma > wrote: > >> > >> Sorry, I don’t follow. > >> Why not get the appender’s layout and get the charset by calling >

Re: org.apache.logging.log4j.core.layout.AbstractStringLayout.getContentType() does not use Charset

returned the right thing, I would not need a conditional. Gary > > > > > On Mar 7, 2018, at 7:21, Gary Gregory wrote: > > > > Here is my current use case: I'd like to be able to query > getContentType() > > on an FILE appender (File, RollingFile, RAF,

Re: org.apache.logging.log4j.core.layout.AbstractStringLayout.getContentType() does not use Charset

et > separately makes semantic sense to me. > > On 6 March 2018 at 16:04, Gary Gregory wrote: > > > Right. AbstractStringLayout says: > > > > @Override > > public Charset getCharset() { > > return charset; > > } > > > &g

Re: org.apache.logging.log4j.core.layout.AbstractStringLayout.getContentType() does not use Charset

Shameless plug) Every java main() method deserves http://picocli.info > > > On Mar 7, 2018, at 1:37, Gary Gregory wrote: > > > > Hi All, > > > > It looks > > like org.apache.logging.log4j.core.layout.AbstractStringLayout. > getContentType() > >

org.apache.logging.log4j.core.layout.AbstractStringLayout.getContentType() does not use Charset

Hi All, It looks like org.apache.logging.log4j.core.layout.AbstractStringLayout.getContentType() does NOT use its charset. Can anyone foresee a problem with fixing this? Gary

Re: release 2.11.0 site

The site is using an old version of maven-site-plugin which in turns depends (IIRC) on a version of Apache BCEL that does not know what to do with Java 8 and/or 9 byte codes. I'm pretty sure that the current version of maven-site-plugin (3.7) has updated its dependency on BCEL to the latest where

Re: JDK 10: Release Candidate & JDK 11 Early Access builds available

How about 2.11.0? Gary On Fri, Mar 2, 2018 at 8:55 AM, Gary Gregory wrote: > But they are removing a bunch of stuff... luckily that we do not depend on. > > Gary > > On Fri, Mar 2, 2018 at 8:15 AM, Remko Popma wrote: > >> I didn't see anything in http://jdk.j

Re: JDK 10: Release Candidate & JDK 11 Early Access builds available

But they are removing a bunch of stuff... luckily that we do not depend on. Gary On Fri, Mar 2, 2018 at 8:15 AM, Remko Popma wrote: > I didn't see anything in http://jdk.java.net/10/release-notes that seemed > relevant for Log4j... > > On Sat, Mar 3, 2018 at 12:05 AM, Ralph Goers > wrote: > >

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

This was fixed by updating to the latest plugin version a couple of days ago. Gary On Mon, Feb 19, 2018, 22:29 Gary Gregory wrote: > The MongoDB failures could be > https://github.com/flapdoodle-oss/de.flapdoodle.embed.mongo/issues/167 > > I'll take a look tomorrow at som

Re: [log4j] providing sourcewith Message

On Fri, Feb 23, 2018 at 7:02 PM, Jeffrey Shaw wrote: > Hi All, > I spent some more time on this tonight. I've brought my code up to date for > log4j versions 2 and 3. version 2 > location-release-2.x> > version > 3

[proposal] Should we drop Java 9 "features" like module-info and multi-release jars or provide it differently.

Hi All: https://issues.apache.org/jira/browse/LOG4J2-2173 is yet another example of a jar (ours) breaking an application as it attempts to support Java 9. It really does not matter that code is not supposed to look at class files in a jar here or there (I'm looking at you META-INF); or that they c

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

The MongoDB failures could be https://github.com/flapdoodle-oss/de.flapdoodle.embed.mongo/issues/167 I'll take a look tomorrow at some point. Gary On Mon, Feb 19, 2018 at 8:30 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See

Re: Log4j Jenkins builds

On Sun, Feb 18, 2018 at 12:44 AM, Ralph Goers wrote: > While splitting out components into modules should have had the desired > effect of reducing the dependencies in log4j-core, it didn’t help making > the builds take less time. The Jenkins build for 3.x took about 43 minutes > while the 2.x b

Re: Jenkins build is unstable: Log4j 2 3.x #1

I've seen that happen on Windows only, which this is not. On Windows this seems to be a MongoDB packaging bug which surfaces as: https://github.com/flapdoodle-oss/de.flapdoodle.embed.mongo/issues/232 and https://jira.mongodb.org/browse/SERVER-32877 But since this is Linux... I'll try the same

Re: [1/2] logging-log4j2 git commit: LOG4J2-2250 The internal status logger timestamp format is now configurable with system property `log4j2.StatusLogger.dateformat`.

On Fri, Feb 16, 2018 at 8:40 AM, Ralph Goers wrote: > > > > On Feb 16, 2018, at 8:34 AM, Gary Gregory > wrote: > > > > On Fri, Feb 16, 2018 at 8:32 AM, Jochen Wiedmann < > jochen.wiedm...@gmail.com <mailto:jochen.wiedm...@gmail.com>> > > wrote

Re: [1/2] logging-log4j2 git commit: LOG4J2-2250 The internal status logger timestamp format is now configurable with system property `log4j2.StatusLogger.dateformat`.

On Fri, Feb 16, 2018 at 8:32 AM, Jochen Wiedmann wrote: > On Fri, Feb 16, 2018 at 4:03 PM, Gary Gregory > wrote: > > On Fri, Feb 16, 2018 at 7:03 AM, Matt Sicker wrote: > > > >> Is this property name already set in stone? Why not log4j2. > >> StatusLogger.D

Re: [1/2] logging-log4j2 git commit: LOG4J2-2250 The internal status logger timestamp format is now configurable with system property `log4j2.StatusLogger.dateformat`.

On Fri, Feb 16, 2018 at 7:03 AM, Matt Sicker wrote: > Is this property name already set in stone? Why not log4j2. > StatusLogger.DateFormat? > +1 Gary > > On 15 February 2018 at 21:59, wrote: > > > Repository: logging-log4j2 > > Updated Branches: > > refs/heads/release-2.x 8e803e788 -> 758

Re: Java 7 as well as future JDK support strategy.

he next release to use. This is all awful. MR jars, Modules, and now this. What a stinking pile :-( Gary > > Ralph > > > On Feb 13, 2018, at 5:50 PM, Gary Gregory > wrote: > > > > On Tue, Feb 13, 2018 at 5:17 PM, Ralph Goers > > > wrote: > > >

Re: Java 7 as well as future JDK support strategy.

ot support Java 10+ features. The multi-release > jar was introduced to explicitly allow us to do that, although I agree it > is unfortunate that it was done in a way that causes so much grief. > > Ralph > > > On Feb 13, 2018, at 5:10 PM, Gary Gregory > wrote: > > &g

Re: Java 7 as well as future JDK support strategy.

lease jars are causing in tool chains and Java modules feel like OSGi NIH. I would be happy to sit on Java 8 for a while. Gary > Ralph > > > On Feb 13, 2018, at 3:26 PM, Gary Gregory > wrote: > > > > On Mon, Feb 12, 2018 at 9:44 PM, Ralph Goers > > > wrote: &

Re: Java 7 as well as future JDK support strategy.

On Mon, Feb 12, 2018 at 9:44 PM, Ralph Goers wrote: > I found this update that says Oracle has extended the public support of > Java 8 about 4 months past the release of Java 11. > https://www.infoq.com/news/2018/02/Java8SupportJan18 < > https://www.infoq.com/news/2018/02/Java8SupportJan18> > I

Re: Java 8

Hi All: Any thoughts on the timing for 2.11.0? Gary On Mon, Jan 29, 2018 at 3:00 PM, Remko Popma wrote: > I will fix picocli before we get to that point. > > (Shameless plug) Every java main() method deserves http://picocli.info > > > On Jan 30, 2018, at 4:07, Gary Gregory

Re: [log4j] NUL in log event message

://picocli.info > > > > > On Feb 9, 2018, at 5:03, Gary Gregory wrote: > > > > > > It might be a bug in JAnsi's WindowsSupport.getLastErrorMessage() > > > > > > Gary > > > > > > On Thu, Feb 8, 2018 at 12:42 PM, Ralph Goers &

Re: [log4j] NUL in log event message

It might be a bug in JAnsi's WindowsSupport.getLastErrorMessage() Gary On Thu, Feb 8, 2018 at 12:42 PM, Ralph Goers wrote: > Maybe this is a silly question, but in what world is it rational to have > NULL chars in the middle of a String? > > Ralph > > > On Feb

[log4j] NUL in log event message

In some cases I get: 2018-02-08 10:14:49,488 main WARN Unable to instantiate org.fusesource.jansi.WindowsAnsiOutputStream due to java.io.IOException: Could not get the screen info: T What you do not see above is that on the console there is more after the "T". There is a NUL character and "h e

Re: [log4j] clarify "internal" vs exported packages in core - plugin API

On Jan 31, 2018 13:30, "Ralph Goers" wrote: Barring something I am unaware of I should be able to do it this weekend. Awesome! :-) Gary Ralph > On Jan 31, 2018, at 12:44 PM, Gary Gregory wrote: > > On Tue, Jan 30, 2018 at 11:14 AM, Gary Gregory > wrote: > >&

Re: [log4j] clarify "internal" vs exported packages in core - plugin API

On Tue, Jan 30, 2018 at 11:14 AM, Gary Gregory wrote: > > > On Jan 30, 2018 11:11, "Ralph Goers" wrote: > > That is all true, but that doesn’t require creating a new 3.0 branch. Or > maybe I misunderstood what you meant by your use of “label". Yes, master >

Re: [1/2] logging-log4j2 git commit: LOG4J2-2236 Removed unnecessary dependency on jcommander since Log4j uses embedded picocli since 2.9.

necessary dependency on jcommander since Log4j uses > embedded picocli since 2.9. > > + > >due-to="Anthony Maire"> > > Added support for precise (micro and nanosecond) timestamps when > running on Java 9. A limited number of precise %d date f

Re: [log4j] The shape of Log4j

On Tue, Jan 30, 2018 at 1:29 PM, Gary Gregory wrote: > > On Tue, Jan 30, 2018 at 1:05 PM, Matt Sicker wrote: > >> It looks like you can use jdeps for this. >> > > The code to support the packages option is commented out :-( even in > current snapshots: > > h

Re: [log4j] The shape of Log4j

plugin/jdeps/AbstractJDepsMojo.java;h=35b322a7d8683e3dd2c6cfa97370c3b25330763a;hb=HEAD Gary > > On 29 January 2018 at 16:11, Gary Gregory wrote: > > > On Mon, Jan 29, 2018 at 2:39 PM, Matt Sicker wrote: > > > > > On 29 January 2018 at 13:10, Gary Gregory &g

Re: [log4j] clarify "internal" vs exported packages in core - plugin API

else. My goal would be to get 2.11.0 out as quickly as possible. That's music to my ears :-) Gary Ralph > On Jan 30, 2018, at 9:21 AM, Gary Gregory wrote: > > On Tue, Jan 30, 2018 at 9:15 AM, Ralph Goers > wrote: > >> Why? >> > > We have a new branch f

Re: [log4j] clarify "internal" vs exported packages in core - plugin API

he 2.x-release branch was that there were too many changes in master for 2.11.0 and that due to the modular work going on with BC-breaking changes in Core, this would warrant a major version change. Gary > Ralph > > > On Jan 30, 2018, at 8:15 AM, Gary Gregory > wrote: > > >

Re: [log4j] Jenkins info

ilures in the past. They might not be > relevant anymore, though. > > On 29 January 2018 at 14:59, Gary Gregory wrote: > > > Hi All: > > > > Our build is on !jenkins-cloud-4GB&&(ubuntu)&&!(ubuntu-eu2) > > <https://builds.apache.org/label/!jenkins-

Re: [log4j] clarify "internal" vs exported packages in core - plugin API

gt; Having a 3.0 release doesn’t necessarily mean we immediately start > > >>>> requiring Java 8. That can could come in a subsequent release. > > >>>> > > >>>> > > >>>> > > >>>>> On Tue, Jan 30, 2018 at

Re: logging-log4j2 git commit: LOG4J2-2236 Removed unnecessary dependency on jcommander since Log4j uses embedded picocli since 2.9.

Will you port to master? Gary On Jan 30, 2018 07:03, wrote: > Repository: logging-log4j2 > Updated Branches: > refs/heads/release-2.x 21bc3aa3b -> 4da4243f5 > > > LOG4J2-2236 Removed unnecessary dependency on jcommander since Log4j uses > embedded picocli since 2.9. > > > Project: http://git-

Fwd: [logging-log4j2] Git Push Summary

We need another Jenkins build for this. We should also change the POM version in git master to avoid mixing things up. Gary -- Forwarded message -- From: Date: Jan 30, 2018 06:51 Subject: [logging-log4j2] Git Push Summary To: Cc: Repository: logging-log4j2 > Updated Branches: >

Re: [log4j] clarify "internal" vs exported packages in core - plugin API

ore > >> all this modularization work and then created a branch so we could > maintain > >> it if necessary. > >> > >> Ralph > >> > >> > On Jan 29, 2018, at 10:04 AM, Gary Gregory > >> wrote: > >> > > >> > On Mon, Jan

Re: [log4j] The shape of Log4j

On Mon, Jan 29, 2018 at 2:39 PM, Matt Sicker wrote: > On 29 January 2018 at 13:10, Gary Gregory wrote: > > > > Speaking of java.sql (and javax.sql): How can we get the Maven build to > > FAIL if log4-core Java codes uses java[x].sql code? > > > > I'm not s

Re: [log4j] org.apache.logging.log4j.core.appender.mom.jeromq move?

On Sun, Jan 28, 2018 at 9:17 PM, Gary Gregory wrote: > Beyond these moves, the next slice and dice would be to deal with our XML, > JSON, and YAML dependencies: > > We have no dependencies to read an XML configuration. > > For JSON and YAML configs, we use Jackson. > >

Re: [log4j] The shape of Log4j

master. How would we deal with dependencies on Apache Commons Compress for example? Just slice and dice the code to minimize the code depending on CC and put that in a new module log4j-compress? Gary > On 27 January 2018 at 16:06, Gary Gregory wrote: > > > As a first cut I was thin

[log4j] Jenkins info

Hi All: Our build is on !jenkins-cloud-4GB&&(ubuntu)&&!(ubuntu-eu2) ) What does that mean and why? Gary

Re: [log4j] The shape of Log4j

On Mon, Jan 29, 2018 at 7:20 AM, Gary Gregory wrote: > > > On Sun, Jan 28, 2018 at 9:35 PM, Matt Sicker wrote: > >> That's rather limiting. Here's what we're already using: >> >> * java.compiler: annotation processing (could potentially be spli

<    5   6   7   8   9   10   11   12   13   14   >