Well, the question and concern should be : "why does mina log so little ?"
In my mind, logging is really a must for any product, and especially for a
framework. It helps users to understand what is happening, and also people
who maintain the code to be able to understand user's problem, just asking
them for smething more interesting and helpfull than a stacktrace.
It may be just me, but I feel that mina is not logging enough, so targeting
a "*NO* dependency just because of this lack of logs is a way to say that
you don't need shampoo because you are bold ;)
As we say in France : "Pas de bras, pas de chocolat " ;)
PS: i'm not saying that Mina is badly written, just in case somone
misinterpreted my opinion :)
Emmanuel
On 8/1/06, Julien Vermillard (JIRA) <[EMAIL PROTECTED]> wrote:
[
http://issues.apache.org/jira/browse/DIRMINA-233?page=comments#action_12424888]
Julien Vermillard commented on DIRMINA-233:
-------------------------------------------
+1 I agree with Peter, the usage of logging MINA do is pretty small for
having a dependency
> Provide an extra thin logging layer for those who don't want SLF4J
> ------------------------------------------------------------------
>
> Key: DIRMINA-233
> URL: http://issues.apache.org/jira/browse/DIRMINA-233
> Project: Directory MINA
> Issue Type: Task
> Reporter: Trustin Lee
>
> As MINA gets more and more popular, the number of people who doesn't
want SLF4J increased because they were using other logging frameworks such
as Log4J or commons-logging. We know SLF4J provides what exactly Log4J or
commons-logging provides, but it's just a matter of preference. We need to
meet as many people's preference as we can as a general network application
framework.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
Cordialement,
Emmanuel Lécharny
