Re: Log42j

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. Johannes ##

Re: Log42j

2015-05-29 8:20 GMT+02:00 Joseph Walton : > >> On 29 May 2015, at 3:55 pm, Lukasz Lenart wrote: > ... >> My assumption was that we do this in Struts 3 - drop other layers and >> use Log4j2 as a main layer. >> >> What do you think about that? > > As long as you’re making changes to logging, have yo

Re: Log42j

> On 29 May 2015, at 3:55 pm, Lukasz Lenart wrote: ... > My assumption was that we do this in Struts 3 - drop other layers and > use Log4j2 as a main layer. > > What do you think about that? As long as you’re making changes to logging, have you given consideration to making SLF4J the standard

Log42j

Hi, Johannes started transforming Struts to use Log4j2 as a base logging layer but I thought it'd just affect LoggingFactory in the way that the Log4j2 would be the first option to consider when looking for available logging layers on classpath. With the current approach user can be surprised tha

Log4j2 doesn't work with Google AppEngine

After switching to Log4j2 we broke all deployments to Google AppEngine :) Maybe you have idea what to do? I'm going to ask on Log4j2 list Uncaught exception from servlet java.lang.ExceptionInInitializerError at org.apache.logging.log4j.status.StatusLogger.(StatusLogger.java:55) at org.apache.loggi

Jenkins build is back to stable : Struts-JDK7-master #302

See - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]