Yes the old implementation is just marked as deprecated so no third party plugins should crash. Users could just use the log4j(1) bridge it's also usefully if you use other third party components.
http://logging.apache.org/log4j/2.x/log4j-1.2-api/index.html Indeed the Google App Engine problem is silly. ################################################# web: http://www.jgeppert.com twitter: http://twitter.com/jogep 2015-05-29 9:36 GMT+02:00 Lukasz Lenart <[email protected]>: > 2015-05-29 8:59 GMT+02:00 Johannes Geppert <[email protected]>: > > I would not say that this change is to big for this release. > > I mean we drop 4 plugins and change to JDK7. > > So adding a new dependency is not such a big change. > > And with log4j2 the users can simply add a bridge. > > So the migration path is not so hard and requires no code changes. > > Do I get it right that plugins which use the old logging facade will > work without issue? And by default, even for old code, everything will > be routed to Log4j2? > > > Regards > -- > Łukasz > + 48 606 323 122 http://www.lenart.org.pl/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
