I don't have a strong preference on JCL vs SLF4J, as I haven't
personally experienced many CL issues using JCL.
But I'm curious, if SLF4J is good enough for large open-source
projects like Spring (OSGI), Hibernate, and MINA to standardize on,
why is it not good enough for JSecurity?
To mitigate the size of the download, you could always distribute a
jsecurity.zip and jsecurity-with-dependencies.zip just like Spring does.
On Jul 17, 2008, at 11:34 AM, Les Hazlewood wrote:
Ah, I see what he/you were saying now, and yes, I agree with that.
My POV
is that it is not worth arguing about any more until a *need*
surfaces.
On Thu, Jul 17, 2008 at 11:33 AM, Emmanuel Lecharny <[EMAIL PROTECTED]
>
wrote:
Les Hazlewood wrote:
Maybe you didn't read the email thoroughly:
Alan just said that when you wrote :
"I will be happy to re-visit this issue if end-users start to
complain
about JCL or express a definite *need* for SLF4J..."
this is your POV, not the community POV. If we decide that we need
to move
to SLF4J, as a community, then we will do it, even if users don't
complain
about CL issues. If we need a formal vote about it, then let's vote.
That being said, reverting the code to its previous state before
injecting
it to Apache was the best thing to do, IMO.
Thanks !
--
--
cordialement, regards,
Emmanuel Lécharny
www.iktek.com
directory.apache.org
