> On Jun 26, 2023, at 2:57 PM, Tim Perry <tim.v...@gmail.com> wrote: > > > >> On Jun 26, 2023, at 1:38 PM, Ralph Goers <ralph.go...@dslextreme.com> wrote: >> >> >> >>> On Jun 26, 2023, at 12:17 PM, Piotr P. Karwasz <piotr.karw...@gmail.com> >>> wrote: >>> >>> Hi Ralph, >>> >>> On Mon, 26 Jun 2023 at 20:33, Ralph Goers <ralph.go...@dslextreme.com> >>> wrote: >>>>> On Jun 25, 2023, at 11:32 PM, Piotr P. Karwasz <piotr.karw...@gmail.com> >>>>> wrote: >>>>> >>>>> Hi Tim, >>>>> >>>>>> On Sat, 24 Jun 2023 at 22:00, Tim Perry <tim.v...@gmail.com> wrote: >>>>>>> >>>>>>> Can we publish log4j-core so it spits out a deprecation warning and just >>>>>>> pulls in log4j-impl or log4j-runtime or whatever? >>>>>> >>>>>> This is probably the best solution. >>>> >>>> How can it be implemented? >>> >>> We replace `log4j-core` with an empty JAR file with `log4j-impl` as >>> dependency. >> >> I can’t say I am thrilled with this idea but I also can’t point to any >> concrete problems it would cause without testing > > It would need a class which prints a depreciation warning at startup as well. > Preferably with directions to fix. > > I’m not thrilled by this, but at least it helps them along. > > Possibly better to stick with log4j-core
Yeah - I think it is better to fix the web site. Separate Log4j-API to its own site. Then see where we are. Ralph
