Can we publish log4j-core so it spits out a deprecation warning and just
pulls in log4j-impl or log4j-runtime or whatever? That might address
Ralph's concern. If we can't avoid the issues Ralph describes, then I'd
vote -1 too.
On Thu, Jun 22, 2023 at 8:13 AM Ralph Goers
wrote:
> Pretend for a mo
The only thing I am aware of is a “relocation” -
https://maven.apache.org/guides/mini/guide-relocation.html. This would mean
continuing to publish log4j-core and have to reference the new artifact.
However, I recall doing that was attempted to redirect log4j 1.x to reload4j
and I don’t recall t
Hi Ralph,
On Sun, 25 Jun 2023 at 00:23, Ralph Goers wrote:
>
> The only thing I am aware of is a “relocation” -
> https://maven.apache.org/guides/mini/guide-relocation.html. This would mean
> continuing to publish log4j-core and have to reference the new artifact.
> However, I recall doing tha
