I don't agree at all with him. He is lazy and does not split up his project into library and application/REPL properly.
However, this is yet another proof that the concept of a generic logging facade, like SLF4J or commons-logging, is flawed. On Thu, May 5, 2016 at 10:04 PM, Matt Sicker <[email protected]> wrote: > >For what it is worth, my own advice is that libraries and framework > developers should always include the slf4j-nop if they use slf4j-api. If > their end-users want logging, they can always use dependency exclusions to > enable it. > > That sounds like it'd make it harder for the users than necessary. Plus, > getting a log message letting me know that I didn't configure logging > properly is useful in case I did mess up something. > > I do like how that article is formatted, though. Adding bibliography info > to your technical articles is pretty neat. > > On 5 May 2016 at 14:54, Ralph Goers <[email protected]> wrote: > >> Maybe, but I can’t really agree with his conclusion. >> >> Ralph >> >> On May 5, 2016, at 12:40 PM, Gary Gregory <[email protected]> wrote: >> >> http://www.russet.org.uk/blog/3112 >> >> G >> >> -- >> E-Mail: [email protected] | [email protected] >> Java Persistence with Hibernate, Second Edition >> <http://www.manning.com/bauer3/> >> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/> >> Spring Batch in Action <http://www.manning.com/templier/> >> Blog: http://garygregory.wordpress.com >> Home: http://garygregory.com/ >> Tweet! http://twitter.com/GaryGregory >> >> >> > > > -- > Matt Sicker <[email protected]> > -- [image: MagineTV] *Mikael Ståldal* Senior software developer *Magine TV* [email protected] Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com Privileged and/or Confidential Information may be contained in this message. If you are not the addressee indicated in this message (or responsible for delivery of the message to such a person), you may not copy or deliver this message to anyone. In such case, you should destroy this message and kindly notify the sender by reply email.
