felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Watson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FELIX-3517) Use of internal Logger seems not worth it
Date Mon, 21 May 2012 19:11:40 GMT

    [ https://issues.apache.org/jira/browse/FELIX-3517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13280378#comment-13280378

Thomas Watson commented on FELIX-3517:

I'm fine with keeping the abstraction, I was just surprised when I found it only being used
in one place and I was contemplating using it in other places in case we need to trace other
things.  For example dynamic imports etc.
> Use of internal Logger seems not worth it
> -----------------------------------------
>                 Key: FELIX-3517
>                 URL: https://issues.apache.org/jira/browse/FELIX-3517
>             Project: Felix
>          Issue Type: Bug
>          Components: Resolver
>         Environment: All
>            Reporter: Thomas Watson
> This may be a point in time issue, but the use of the internal logger (org.apache.felix.resolver.Logger)
seems a bit overboard since it is only used in one place in the method org.apache.felix.resolver.ResolverImpl.checkPackageSpaceConsistency
> Should we be adding more usages of this logger for debugging or is it really intended
to be used to debug class space consistency issues?

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message