Hello, before creating a pull request I would like to get feedback whether I am the only one who thinks this logging mixture strange :-).
Regards Mirko Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen) https://bitbucket.org/mfriedenhagen/ On Sat, Aug 29, 2015 at 5:46 PM, Mirko Friedenhagen <[email protected]> wrote: > Hello, > > after the task scanner plugin was complaining about a missing log4j > configuration file, I took a look at the included dependencies in the war > and found: > > - commons-logging > - log4j > - slf4j-api > - slf4j-jd14 > > This is a weird mixture: > - everything using the slf4j-api will use the standard two line > java.util.logging. > - everything using commons-logging or log4j directly will use log4j and this > one is not configured so either they show up in the console output or are > redirected to stderr or are lost in the dark. > > I propose we mark log4j and commons-logging as provided and add > log4j-over-slf4j and jcl-over-slf4j as runtime or compile dependencied so > everything will use java.until.logging in the end. > > What do you think? > > Regards > Mirko > -- > Sent from my mobile -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAK8jvqxj9Oxz69SLqUcTXipdVv7C1kasdqQYr5%2BddR6fu5kd_g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
