commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebb (JIRA)" <>
Subject [jira] [Commented] (DISCOVERY-15) implementing a commons-logging wrapper is an overkill
Date Tue, 05 Apr 2011 10:31:05 GMT


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:
>             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:

View raw message