Re: XML Calabash and logging

I would tend to agree with Leif, and as you know we do use Calabash as a library . We’re using slf4j locally here too, and have no dependency to log4j2 so far. But it’s not a strong argument, as we can always use a log4j-to-slf4j adapter.

Romain.


On 3 sept. 2014, at 22:24, Leif Warner <abimelech@gmail.com> wrote:

> If Calabash is available for use as a library, I'd recommend coding against SLF4J, not a specific logging impl.  Many projects I work on use SLF4J, and when libraries code against that, the final product is free to chose between logback or log4j or whatever as the logging impl.  I think of SLF4J as a sort of unifying API for all sorts of disparate libraries to have their log messages go through the same system (e.g. not having to manage seperate logging.conf files for each). Not terribly familiar w/ log4j2, though. And if this is just a command-line app and not a library, what does it matter?
> 
> 
> On Wed, Sep 3, 2014 at 12:05 PM, Norman Walsh <ndw@nwalsh.com> wrote:
> Offline, David is encouraging me to just skip SLF4J and use
> LOG4J2. Anyone have reason to be opposed?
> 
>                                         Be seeing you,
>                                           norm
> 
> --
> Norman Walsh
> Lead Engineer
> MarkLogic Corporation
> Phone: +1 512 761 6676
> www.marklogic.com
>