[ https://issues.apache.org/jira/browse/NUTCH-1078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13116308#comment-13116308 ]
Julien Nioche commented on NUTCH-1078: -------------------------------------- I had modified LogUtil in 2.0 (see http://svn.apache.org/viewvc/nutch/branches/nutchgora/src/java/org/apache/nutch/util/LogUtil.java?view=markup). A simple option would be to copy the version from 2.0 to trunk but getting rid of it altogether is fine too. Let's go for whatever is quickest, we can't have the trunk broken like this > 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 > > > 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