You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@commons.apache.org by "Sebb (JIRA)" <ji...@apache.org> on 2011/04/05 12:31:05 UTC

[jira] [Commented] (DISCOVERY-15) implementing a commons-logging wrapper is an overkill

    [ https://issues.apache.org/jira/browse/DISCOVERY-15?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015840#comment-13015840 ] 

Sebb commented on DISCOVERY-15:
-------------------------------

According to the SVN history, these classes were added because:

"Added logging support.  Copied 2 files from commons-logging (Log & LogFactory)
to prevent circular dependencies during build.  Support for a bootstrap mechanism
to allow the default (VERY simple logging) to be replaced with app/system loggers."

Not entirely sure where the circular dependency comes from, unless commons logging once depended on discovery?


> implementing a commons-logging wrapper is an overkill
> -----------------------------------------------------
>
>                 Key: DISCOVERY-15
>                 URL: https://issues.apache.org/jira/browse/DISCOVERY-15
>             Project: Commons Discovery
>          Issue Type: Improvement
>    Affects Versions: 0.5
>            Reporter: Simone Tripodi
>            Assignee: Simone Tripodi
>             Fix For: 0.5
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> org.apache.commons.discovery.log is a commons-logging implementation wrapper, moreover the 90% of classes that use a Log instance, have a static setter method.
> It should be enough just using commons-logging in the 'traditional' way :P

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira