Re: [ANNOUNCE] Apache Log4j 2.9.1 released

Blogged: https://blogs.apache.org/logging/entry/log4j-2-9-1-released (Shameless plug) Every java main() method deserves http://picocli.info > On Sep 22, 2017, at 9:32, Ralph Goers wrote: > > As of Log4j 2.9.0, the Log4j API was modified to use

[ANNOUNCE] Apache Log4j 2.9.1 released

The Apache Log4j 2 team is pleased to announce the Log4j 2.9.1 release! Apache Log4j is a well known framework for logging application behavior. Log4j 2 is an upgrade to Log4j that provides significant improvements over its predecessor, Log4j 1.x, and provides many other modern features such as

Re: [VOTE] Release Log4j 2.9.1-rc1

Okay. I'll update the draft blog post when I see your email. By the way, would it be possible to modify the announcement text for LOG4J2-2035 to "Fix documentation to clarify disruptor-3.3.4 is now required for async loggers (previously the docs referred to disruptor-3.3.3 which was never

Release Announcement: General Availability of JDK 9

This was copied from another list. We stopped getting these emails when we merged all the dev lists and Rory doesn’t seem to have fixed the problem. Ralph Three items to share with you today JDK 9 General Availability GPL'd binaries from Oracle are available here: http://jdk.java.net/9

Re: [VOTE] Release Log4j 2.9.1-rc1

I changed it some, yes. Ralph > On Sep 21, 2017, at 2:55 PM, Remko Popma wrote: > > I started writing the blog post for 2.9.1. > Quick question: no changes to the announcement text this time, is that > correct? > > On Thu, Sep 21, 2017 at 1:12 PM, Ralph Goers

Re: logging-log4j2 git commit: Fix wording of 2.9.1 change item (LOG4J2-2035)

Ralph, Would it be possible to include the new wording in the 2.9.1 announcement email? Remko > On Sep 22, 2017, at 7:17, rpo...@apache.org wrote: > > Repository: logging-log4j2 > Updated Branches: > refs/heads/master 3f5d58cd3 -> 8b5d644d5 > > > Fix wording of 2.9.1 change item

[jira] [Commented] (LOG4J2-2035) There is no such lib as disruptor-3.3.3

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

Re: [VOTE] Release Log4j 2.9.1-rc1

I started writing the blog post for 2.9.1. Quick question: no changes to the announcement text this time, is that correct? On Thu, Sep 21, 2017 at 1:12 PM, Ralph Goers wrote: > My +1 > > Ralph > > > On Sep 18, 2017, at 12:07 AM, Ralph Goers

Re: [log4j] "JDK 9 Ready"

Also, I plan on adding the manifest headers so Log4j classifies as somewhat modularized before the next release. Ralph > On Sep 21, 2017, at 1:08 PM, Ralph Goers wrote: > >> >> On Sep 21, 2017, at 9:36 AM, Gary Gregory wrote: >> >> On

Re: [log4j] "JDK 9 Ready"

> On Sep 21, 2017, at 9:36 AM, Gary Gregory wrote: > > On Thu, Sep 21, 2017 at 9:39 AM, Ralph Goers > wrote: > >> >>> On Sep 21, 2017, at 7:35 AM, Gary Gregory >> wrote: >>> >>> Hi, >>> >>> Oracle has asked me if

Re: [log4j] "JDK 9 Ready"

On Thu, Sep 21, 2017 at 9:39 AM, Ralph Goers wrote: > > > On Sep 21, 2017, at 7:35 AM, Gary Gregory > wrote: > > > > Hi, > > > > Oracle has asked me if we have an official announcement that we are "JDK > 9 > > ready". Do we? > > > > We are

Re: [log4j] "JDK 9 Ready"

> On Sep 21, 2017, at 7:35 AM, Gary Gregory wrote: > > Hi, > > Oracle has asked me if we have an official announcement that we are "JDK 9 > ready". Do we? > > We are listed here: > https://wiki.openjdk.java.net/display/quality/Quality+Outreach >

[log4j] "JDK 9 Ready"

Hi, Oracle has asked me if we have an official announcement that we are "JDK 9 ready". Do we? We are listed here: https://wiki.openjdk.java.net/display/quality/Quality+Outreach Gary