[jira] [Commented] (NUTCH-1078) Upgrade all instances of commons logging to slf4j (with log4j backend)

["Lewis John McGibbney (JIRA)" <ji...@apache.org>]

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

Lewis John McGibbney commented on NUTCH-1078:
---------------------------------------------

This issue is inherently large to deal with and it would need to be phased in my opinion. Almost every class we maintain contains commons logging imports and usage. Ultimately it would mean that we could drop a couple project dependencies from runtime if implemented fully across the whole Nutch code base.

I know that this is pretty vague but does anyone have ideas for progressing... it was not my intention to unearth quite this large a task. Thanks

> Upgrade all instances of commons logging to slf4j (with log4j backend)
> ----------------------------------------------------------------------
>
>                 Key: NUTCH-1078
>                 URL: https://issues.apache.org/jira/browse/NUTCH-1078
>             Project: Nutch
>          Issue Type: Improvement
>    Affects Versions: 1.4, 2.0
>            Reporter: Lewis John McGibbney
>            Assignee: Lewis John McGibbney
>            Priority: Minor
>             Fix For: 1.4, 2.0
>
>
> Whilst working on another issue, I noticed that some classes still import and use commons logging for example HttpBase.java
> {code}
> import java.util.*;
> // Commons Logging imports
> import org.apache.commons.logging.Log;
> import org.apache.commons.logging.LogFactory;
> // Nutch imports
> import org.apache.nutch.crawl.CrawlDatum;
> {code}
> At this stage I am unsure how many (if any others) still import and reply upon commons logging, however they should be upgraded to slf4j for branch-1.4 and trunk 2.0 respectively.

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