[ 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-branch-1.4-20110816.patch patch attachment for branch-1.4. This upgrades all instances of Jakarta Commons Logging to slf4j logging. For reference information can be found on the migration tool here [1]. Some limitation which I need to check is if any logging constructs of non-string type have been missed, as well as build scripts. [1] http://www.slf4j.org/migrator.html > 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 > > Attachments: NUTCH-1078-branch-1.4-20110816.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. For more information on JIRA, see: http://www.atlassian.com/software/jira