> On Dec 23, 2021, at 10:07 AM, Vladimir Sitnikov <sitnikov.vladi...@gmail.com> > wrote: > > > Do you know migration to 2.x is not a drop-in replacement? > It might require code or non-trivial configuration changes? > For instance, if the application extends 1.x appenders, implements > non-trivial re-configuration logic, > then it can't upgrade to 2.x in a matter of days or weeks. Do you know that for a fact? Have you tried the support for 1.x appenders, etc? I can’t say it always works but I am quite sure you can’t say it never does. Ralph
- Re: Resurrecting log4j 1.x Ralph Goers
- Re: Resurrecting log4j 1.x Vladimir Sitnikov
- Re: Resurrecting log4j 1.x Gary Gregory
- Re: Resurrecting log4j 1.x Vladimir Sitnikov
- Re: Resurrecting log4j 1.x Gary Gregory
- Re: Resurrecting log4j 1.x Vladimir Sitnikov
- Re: Resurrecting log4j 1.x Gary Gregory
- Re: Resurrecting log4j 1.x Vladimir Sitnikov
- Re: Resurrecting log4j 1.x Dominik Psenner
- Re: Resurrecting log4j 1.x Vladimir Sitnikov
- Re: Resurrecting log4j 1.x Ralph Goers
- Re: Resurrecting log4j 1.x Christian Grobmeier
- Re: Resurrecting log4j 1.x Vladimir Sitnikov
- Re: Resurrecting log4j 1.x Dominik Psenner
- Re: Resurrecting log4j 1.x Ralph Goers
- Re: Resurrecting log4j 1.x Christian Grobmeier
- Re: Resurrecting log4j 1.x Vladimir Sitnikov
- Re: Resurrecting log4j 1.x Remko Popma
- Re: Resurrecting log4j 1.x Christian Grobmeier
- Re: Resurrecting log4j 1.x Andrew Marlow
- Re: Resurrecting log4j 1.x Volkan Yazıcı