[
https://issues.apache.org/jira/browse/NUTCH-1078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lewis John McGibbney updated NUTCH-1078:
----------------------------------------
Attachment: NUTCH-1078-trunk-20110929.patch
The attached patch changes the LogUtil class to accommodate the requirements of
the slf4j framework.
I ask if this could be tested and if necessary I will update other classes as
per my earlier comments.
At this stage in time my thinking is that we should separate the removal of
LogUtil from this issue as they fundamentally, they mean different things for
the Nutch codebase.
> 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
> Reporter: Lewis John McGibbney
> Assignee: Lewis John McGibbney
> Priority: Blocker
> Fix For: 1.4
>
> Attachments: NUTCH-1078-branch-1.4-20110816.patch,
> NUTCH-1078-branch-1.4-20110824-v2.patch,
> NUTCH-1078-branch-1.4-20110911-v3.patch,
> NUTCH-1078-branch-1.4-20110916-v4.patch, NUTCH-1078-trunk-20110929.patch
>
>
> 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.
--
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
