[ https://issues.apache.org/jira/browse/NUTCH-1078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13108741#comment-13108741 ]
Sami Siren commented on NUTCH-1078: ----------------------------------- Lewis, after applying this patch I still see some references to commons-logging in ivy/ivy.xml and some pom.xml files too. I think those should also be removed, no? > 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: Minor > 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 > > > 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