[ http://issues.apache.org/jira/browse/DIRMINA-233?page=comments#action_12424862 ] peter royal commented on DIRMINA-233: -------------------------------------
There are two places in MINA that use a logger. My thought is that we could have our own (very simple) logging abstraction that satisfies what these two places need. Heck, we could even default to slf4j, but allow the user to plug in an alternate implementation either by specifying a system property, or by manually setting it, similar to how the ByteBufferAllocator works. > 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
