Hi Jevon, My intention was to only rely on slf4j for logging. I don't want to force users to use logback (even if it is my preferred choice today). I haven't checked recently but if you are using Maven you should only get slf4j-api in your classpath and no implementation (logback is set to be optional=true so no transitive inclusion). People are free to use any logging framework compatible with slf4j.
Anyway you are right that we should provide in the quickstart a sample of logging configuration. Here using logback is fine, as long as we are clear it is only a possibility, not mandatory. As far as I know apache-httpclient is using commons-logging to log, not logback. In order to avoid commons-logging, the dependency is excluded (see [1]), and jcl-over-slf4j is added to the classpath. It means that every logs are redirected to slf4j. So basically in the quickstart I would better say something like : =Configuring logging= JWebUnit use slf4j to log (link to slf4j website). You can use any implementation you like. For example you can use logback (link to logback website). Here is how to configure logback : 1) If you are using Maven you must add a dependency on logback <dependency> <groupId>ch.qos.logback</groupId> <artifactId>logback-classic</artifactId> <version>1.0.6</version> <scope>runtime</scope> </dependency> 2) You must provide a logback.xml configuration file in your classpath (example + link to logback documentation)... Regards, Julien [1] http://jwebunit.svn.sourceforge.net/viewvc/jwebunit/trunk/jwebunit-htmlunit-plugin/pom.xml?revision=952&content-type=text%2Fplain >________________________________ > De : jevon <je...@jevon.org> >À : JWebUnit Development mail list ><jwebunit-development@lists.sourceforge.net> >Envoyé le : Jeudi 16 août 2012 3h27 >Objet : [JWebUnit-development] Adding sample logback.xml to JWebUnit homepage > >Hi, > >In r951, I've added some brief instructions on how to get the logback >logger to be quiet - by default, if no logback.xml is present, then >ALL logging information (including on-wire transmissions themselves) >will be dumped onto stdout. I've hit this problem twice now so I think >it's probably a good idea to include it in the quick how-to guide. > >See also: http://stackoverflow.com/a/8936580/39531 > >Thoughts? I haven't pushed the changes onto the SF homepage yet (I'm >not sure if I have the permissions anyway). > >Jevon > >------------------------------------------------------------------------------ >Live Security Virtual Conference >Exclusive live event will cover all the ways today's security and >threat landscape has changed and how IT managers can respond. Discussions >will include endpoint security, mobile security and the latest in malware >threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >_______________________________________________ >JWebUnit-development mailing list >JWebUnit-development@lists.sourceforge.net >https://lists.sourceforge.net/lists/listinfo/jwebunit-development > > > ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ JWebUnit-development mailing list JWebUnit-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jwebunit-development
