Weird. I have been running so manyv local builds for changes I check in. I
must have missed that one! Feel free to revert or investigate unless I get
to it first.
Gary
On Oct 21, 2017 08:11, "Mikael Ståldal" wrote:
> The problem started here:
> https://builds.apache.org/job/Log4j%202.x/3135/
>
The problem started here:
https://builds.apache.org/job/Log4j%202.x/3135/
https://github.com/apache/logging-log4j2/commit/9126644cf85a52859690bc8499b0c701a8db3ae7
So I guess that the upgrade from Spring Framework 3.x to 4.x by Gary
caused it.
On 2017-10-19 22:14, Ralph Goers wrote:
I am wond
On 2017-10-20 06:36, Matt Sicker wrote:
On 19 October 2017 at 14:05, Mikael Ståldal wrote:
And don't forget a corresponding LogEventParser.
Right. The basic idea here would be to provide both a reference encoder and
decoder. If an existing binary format such as BSON, Avro, or Thrift were
ap
