Mailing-List: contact dev-help@cayenne.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cayenne.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: cayenne logging
From: Andrus Adamchik <andrus@objectstyle.org>
In-Reply-To: 
 <CAM1yOjZ8a=7htjBBNjgGh8eCGbyCXvq5GO5vVNG0MqJ07HDcrA@mail.gmail.com>
Date: Tue, 23 Apr 2013 09:34:29 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <A8129452-5E48-468C-87C9-A75E32D10505@objectstyle.org>
References: 
 <CAFrHPLEHEH2FSTmDFK2hC2q5gEfh7qEocP44B8hOdxLQajUCFw@mail.gmail.com>
 <CAM1yOjZ8a=7htjBBNjgGh8eCGbyCXvq5GO5vVNG0MqJ07HDcrA@mail.gmail.com>
To: dev@cayenne.apache.org

In my own environment SLF is becoming more and more common. If that is =
the case with everyone else, this would mean that using SLF would mean =
fewer hoops to jump for the majority of users. So I wouldn't mind if we =
switch. But since there are ways to bridge from JCL to SLF, as well as =
from SLF to JCL, theoretically both loggers should work the same =
everywhere. So maybe the solution lies in documenting jcl-over-slf4j.jar =
bridge in our docs?

Andrus


On Apr 23, 2013, at 8:55 AM, Mike Kienenberger <mkienenb@gmail.com> =
wrote:
> My guess would be no, but others may have a different opinion.   Our
> dependencies use commons-logging.
>=20
> But the nice thing about the commons-logging api is that you can
> trivially replace the commons-logging jar files with
> jcl-over-slf4j.jar.
>=20
> I do this now in one of my projects.
>=20
> On Tue, Apr 23, 2013 at 8:06 AM, Juan Jos=E9 Gil <matero@gmail.com> =
wrote:
>> Is there any plan to use slf4j instead of commons-logging with =
cayenne?
>>=20
>> If you need someone who do the nasty work, I would be glad to =
contribute a
>> patch :)
>=20