That doesn’t really work:
1. As soon as there is some bug in it means someone has to go an create the
repo and the appropriate scaffolding to get a release to work. No one will ever
do it.
2. I release cannot consists of stuff from multiple repos. The distribution zip
needs to contain
Hi Ralph,
On Mon, 20 Mar 2023 at 15:09, Apache wrote:
>
> I would be comfortable with this if it is moved to its own repo and released
> first, then removed from the Log4J repo. I am not comfortable with “we can do
> it someday if we want to” unless we are dropping support for it.
Can we keep
I would be comfortable with this if it is moved to its own repo and released
first, then removed from the Log4J repo. I am not comfortable with “we can do
it someday if we want to” unless we are dropping support for it.
Ralph
> On Mar 20, 2023, at 3:36 AM, Volkan Yazıcı wrote:
>
> [TLDR:
[TLDR: Piotr and I propose moving `log4j-jmx-gui` to its own repository to
ease Java 9+ migration for `2.x`, objections?]
In the `2.x` branch, AFAIK, `log4j-jmx-gui` is the only module that has a
Java 8 requirement, i.e., `jconsole.jar`. Piotr and I have been trying to
come up with ways to make
