Ok, fixed for real now:
https://travis-ci.org/apache/logging-log4j2/builds/580008415
On Mon, 2 Sep 2019 at 17:00, Matt Sicker wrote:
>
> I think I've got it working now. See
> https://travis-ci.org/apache/logging-log4j2/builds/579990414 for the
> specific run.
>
> On Mon, 2 Sep 2019 at 16:23, Mat
For some reason, the Reply-To address is being ignored by Gmail for
this message. Anyways, I can't figure out which combination of JDKs to
use for release-2.x. The closest combo I found to work was jdk8+jdk11,
but then there was a unit test failure in the YAML config which is
likely related to jdk7
I think I've got it working now. See
https://travis-ci.org/apache/logging-log4j2/builds/579990414 for the
specific run.
On Mon, 2 Sep 2019 at 16:23, Matt Sicker wrote:
>
> Ok, I'm getting annoyed from all the build failure emails from Travis.
> I'm looking into fixing this now.
>
> On Thu, 1 Aug
Ok, I'm getting annoyed from all the build failure emails from Travis.
I'm looking into fixing this now.
On Thu, 1 Aug 2019 at 13:32, Matt Sicker wrote:
>
> If their documentation is wrong, there are probably two options:
>
> 1. Run find . in a job and look through the file system.
> 2. Use the a
Based on this clarification, we do not need to remove the maven
wrapper jar from our source distributions. I brought this up in the
last release vote, so I'm noting here that it's no longer an issue.
-- Forwarded message -
From:
Date: Sun, 1 Sep 2019 at 21:56
Subject: svn commit:
