Re: [JWebUnit-development] Adding sample logback.xml to JWebUnit homepage

[Julien H. <he...@ya...>]

Just tested and you were right. Logback is taken transitively. It seems the optional=true is not taken into account (maybe because it is in dependency management).

I have commited a fix and updated documentation. Feel free to give me some feedback.

Regards,

Julien



----- Mail original -----
> De : jevon <je...@je...>
> À : Julien HENRY <he...@ya...>; JWebUnit Development mail list <jwe...@li...>
> Cc : 
> Envoyé le : Jeudi 16 août 2012 15h05
> Objet : Re: [JWebUnit-development] Adding sample logback.xml to JWebUnit homepage
> 
> Hi Julien,
> 
> Thanks for your reply :D I might have more time to work on JWebUnit
> over the next few weeks, if anything needs doing. Today I looked at
> implementing JSON POST (for RESTful APIs) but it's probably not
> suitable for inclusion within JWebUnit.
> 
> I didn't try slf4j, only log4j (whose configuration didn't do
> anything). I've stumbled upon this twice, from importing the most
> recent JWebUnit directly into a fresh project that doesn't use any
> logging frameworks or Maven (and if you are using the jars directly,
> it's probably unlikely you're using Maven). If you prefer slf4j, can
> we provide a sample configuration as well? Perhaps the release build
> should include a specific logger.
> 
> This is only to get people up-and-running quickly, I think we should
> write a section on logging and how multiple are supported. The amount
> of noise generated without one makes it difficult to debug. My
> preference is for a sample configuration (copy/paste) for each of the
> supported loggers.
> 
> Jevon
> 
> On Thu, Aug 16, 2012 at 8:22 PM, Julien HENRY <he...@ya...> wrote:
>>  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...@je...>
>>> À : JWebUnit Development mail list 
> <jwe...@li...>
>>> 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
>>> JWe...@li...
>>> 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
>>  JWe...@li...
>>  https://lists.sourceforge.net/lists/listinfo/jwebunit-development
>