Hi Mark, you can use JUL with meecrowave (I do in some integrations) so I guess the discussion is rather: do we contribute to log4j2 to clean it up or do we drop it. I wouldn't go back to log4j1 which is really in maintenance mode and no more adapted to today's apps.
Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://rmannibucau.metawerx.net/> | Old Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book <https://www.packtpub.com/application-development/java-ee-8-high-performance> Le sam. 14 juil. 2018 à 11:41, Mark Struberg <strub...@yahoo.de.invalid> a écrit : > hi folks! > > I've reviewed our use of logging and I wonder if it's really worth it to > use log4j2? > It adds a whoopy 2MB to our bundle. That's quite something :/ > > I'd love to keep the MDC feature. This is really essential for my dayjob. > But log4j1 is just 300kB whereas log4j2 is 2MB. > So is it really worth it? > Note that log4j2 was substantially smaller (900kB) in 2.0 but continuously > grew over the last 2 years. > I've already triggered a discussion over there. > > Wdyt? > Would of course be a MW-2.3.x release. > > LieGrue, > strub > >
