[ https://issues.apache.org/jira/browse/NUTCH-2012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16433869#comment-16433869 ]
Hudson commented on NUTCH-2012: ------------------------------- SUCCESS: Integrated in Jenkins build Nutch-trunk #3517 (See [https://builds.apache.org/job/Nutch-trunk/3517/]) NUTCH-2012 Merge parsechecker and indexchecker - let ParserChecker (snagel: [https://github.com/apache/nutch/commit/24670e97826b674861d70cd3e0551b154466f8ac]) * (edit) src/java/org/apache/nutch/parse/ParserChecker.java * (edit) src/java/org/apache/nutch/indexer/IndexingFiltersChecker.java * (edit) src/java/org/apache/nutch/util/AbstractChecker.java > Merge parsechecker and indexchecker > ----------------------------------- > > Key: NUTCH-2012 > URL: https://issues.apache.org/jira/browse/NUTCH-2012 > Project: Nutch > Issue Type: Improvement > Affects Versions: 1.10 > Reporter: Sebastian Nagel > Assignee: Sebastian Nagel > Priority: Minor > Fix For: 1.15 > > > ParserChecker and IndexingFiltersChecker have evolved from simple tools to > check parsers and parsefilters resp. indexing filters to powerful tools which > emulate the crawling of a single URL/document: > - check robots.txt (NUTCH-2002) > - follow redirects (NUTCH-2004) > Keeping both tools in sync takes extra work (cf. NUTCH-1757/NUTCH-2006, also > NUTCH-2002, NUTCH-2004 are done only for parsechecker). It's time to merge > them > * either into one general debugging tool, keeping parsechecker and > indexchecker as aliases > * centralize common code in one utility class -- This message was sent by Atlassian JIRA (v7.6.3#76005)