OK, I think I will open a PR. log4j and commons-logging should best be set to provided as otherwise they may sneak in in the core as transitive dependency and the plugin parent should probably get something like this as well. Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen) https://bitbucket.org/mfriedenhagen/
On Tue, Sep 1, 2015 at 5:54 PM, James Nord <[email protected]> wrote: >> Hasn’t core PR 1765 already addressed parts of this > > > I Hope so. The commons-logging (still?) needs replacing with the slf4j > interceptor. > > -- > 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/cfbf6443-ec65-4843-b8dd-7bed2604118b%40googlegroups.com. > > For more options, visit https://groups.google.com/d/optout. -- 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/CAK8jvqw7X8fdRV8rOaLgwSLxRaYcN%2BvnL67LrBX3e9u1aoLMyg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
