You can try the bridge to log4j1, this is maybe the simplest solution here.
https://logging.apache.org/log4j/log4j-2.2/log4j-1.2-api/index.html Best Regards Johannes ################################################# web: http://www.jgeppert.com twitter: http://twitter.com/jogep 2016-07-18 15:24 GMT+02:00 Sreekanth S. Nair < sreekanth.n...@egovernments.org>: > Absolutely that's what even i feel, server like Jboss (wildfly doesn't have > support for it) so all logs coming after the following message is writing > to stdout (is that the expected behavior). > > > On Mon, Jul 18, 2016 at 6:43 PM, Emi <em...@encs.concordia.ca> wrote: > > > hi, is there any plan for the date of end of life for 2.3.x series? > >>> > >> No exact date but you can only expect security fixes (if possible) > >> that will ported into 2.3.x series. > >> should consider migrating into 2.5.x series which isn't so hard. > >> > > Will 2.5.x support log4j1.x? There are thousands of classes calling > > log4j1.x. > > > > From log4j1.x to 2.x will be lots of changes. > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: user-unsubscr...@struts.apache.org > > For additional commands, e-mail: user-h...@struts.apache.org > > > > >
