*TL;DR* I propose moving the `log4j-server` module of the `log4j-tools` project to a PR, merging `log4j-maven-shade-plugin-extensions` PR, and releasing `log4j-tools`. Objections?
*Long story* Months months ago, I talked about onboarding the maven-shaded-log4j-transformer <https://github.com/edwgiz/maven-shaded-log4j-transformer> as an official Log4j plugin. It is proven to be working and useful – we use it in the `log4j-perf` module. In a nutshell, it makes the Log4j 2 plugin system work when multi JARs get combined via shading. In succeeding discussions, we decided to use the log4j-tools <https://github.com/apache/logging-log4j-tools> project to host it. In the meantime, I made the original author an offer he couldn't refuse and he kindly landed a PR <https://github.com/apache/logging-log4j-tools/pull/2>. Now... It is time to ship this transformer... but... `log4j-tools` historically never had any releases, yet contains a `log4j-server` module. The what and how of it can be found in the repository. Given it was neither touched, nor released after several years, I think it is in a stale state.
