I have been working on a large commit for 3.0 to change how plugins are bound
and to move the plugin code to its own module. Following that I plan on going
through more Jira issues that are critical. I know of a few that I feel need to
be addressed. Once that is done I will think about pushing a
We should make sure to fix the failing test (possibly dropped events when logs
roll) before we release:
https://issues.apache.org/jira/browse/LOG4J2-2613
I'd love to have the fix for https://issues.apache.org/jira/browse/LOG4J2-2606
available, but that's pending a more thorough review.
On Wed,
Hi All:
I'm seeing https://issues.apache.org/jira/browse/LOG4J2-2612 in our builds
randomly but not that often.
Does anyone plan on doing a release for 2.12.0 anytime soon-ish?
Thank you,
Gary
Hmm, then maybe it's better that I refrain from using forced pushes and
just leave
even trivial changes as separate commits, seems to cause less issues that
way.
On Tue, May 28, 2019 at 8:49 PM Matt Sicker wrote:
> Oh, and note that GitHub isn’t typically that great at notifying people in
> a PR
