Sounds good to me! Might want to re-sync the Log4j version to the latest
release, though.
> On Sep 15, 2023, at 8:00 AM, Volkan Yazıcı wrote:
>
> I renovated `log4j-kotlin` quite a bit and I think we are ready for
> the `1.3.0` release. I share the tentative release notes below to give
> you an
Should be fine to archive as we’re migrated to GHA.
> On Sep 15, 2023, at 2:03 AM, Volkan Yazıcı wrote:
>
> AFAIC, no Logging Services projects use Jenkins pipelines anymore.
> Created INFRA-24991 to archive the `logging-pipelines` repository,
> FYI.
This sounds like a great improvement! As for the single JVM idea, perhaps if we
add tags to tests that require a clean JVM, then we’d be able to run some
subset of tests faster.
> On Sep 18, 2023, at 3:42 AM, Piotr P. Karwasz wrote:
>
> Hi all,
>
> I plan to merge PR #1785[1] soon, which shou
Hi all,
I plan to merge PR #1785[1] soon, which should decrease by 50% the
time we spend waiting for the CI to succeed. This PR switches the
default Surefire mode to running 1C tests in parallel each in its own
JVM (where C is the number of cores available). The order of execution
is deterministic
Hey Gary,
I'd appreciate your response on this `dev@` thread. I am cleaning up all
repositories and trying to either (in order of preference)
1. delete them (since they are practically empty or irrelevant)
2. archive them (clearly communicate it to the users that nobody is
working on the
Apache Log4j JMX GUI[1] team is pleased to announce the 2.21.0
release. This project provides a Swing-based client for remotely
editing the Log4j configuration and remotely monitoring `StatusLogger`
output. It can be run as a standalone application or as a JConsole plugin.
# Release Notes
This ma
