[
https://issues.apache.org/jira/browse/NUTCH-309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris A. Mattmann resolved NUTCH-309.
-------------------------------------
Fix Version/s: 1.2
2.0
Resolution: Won't Fix
I'm closing this out. It's been ~4 years since its creation and Nutch has made
it just fine w/o these logging improvements. If there is a sufficient desire
and need to include them, please open up a new issue and attach a patch. Thanks!
> Uses commons logging Code Guards
> --------------------------------
>
> Key: NUTCH-309
> URL: https://issues.apache.org/jira/browse/NUTCH-309
> Project: Nutch
> Issue Type: Improvement
> Affects Versions: 0.8
> Reporter: Jerome Charron
> Assignee: Chris A. Mattmann
> Priority: Minor
> Fix For: 1.2, 2.0
>
>
> "Code guards are typically used to guard code that only needs to execute in
> support of logging, that otherwise introduces undesirable runtime overhead in
> the general case (logging disabled). Examples are multiple parameters, or
> expressions (e.g. string + " more") for parameters. Use the guard methods of
> the form log.is<Priority>() to verify that logging should be performed,
> before incurring the overhead of the logging method call. Yes, the logging
> methods will perform the same check, but only after resolving parameters."
> (description extracted from
> http://jakarta.apache.org/commons/logging/guide.html#Code_Guards)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
