[ https://issues.apache.org/jira/browse/NUTCH-2292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16784884#comment-16784884 ]
Thamme Gowda commented on NUTCH-2292: ------------------------------------- Last time when I worked on it, we (I and Lewis) had it done mostly except {color:#FF0000}some test cases{color}. (I was able to do mvn{color:#14892c} -DskipTests {color}and the build was good to use). However, the problem with test cases was that some of them (which seem to be treated as unit tests) are actually integration tests and they required to be modified (so as to let maven can run during the integration test phase). This is the blocker: https://issues.apache.org/jira/browse/NUTCH-2293 It came down to the issue of modifying those test cases as integration tests. I was not confident about that unit–> integration conversion. I halted there and never gotten back. > Mavenize the build for nutch-core and nutch-plugins > --------------------------------------------------- > > Key: NUTCH-2292 > URL: https://issues.apache.org/jira/browse/NUTCH-2292 > Project: Nutch > Issue Type: Improvement > Components: build > Reporter: Thamme Gowda > Assignee: Thamme Gowda > Priority: Major > Fix For: 1.16 > > > Convert the build system of nutch-core as well as plugins to Apache Maven. > *Plan :* > Create multi-module maven project with the following structure > {code} > nutch-parent > |-- pom.xml (POM) > |-- nutch-core > | |-- pom.xml (JAR) > | |--src : sources > |-- nutch-plugins > |-- pom.xml (POM) > |-- plugin1 > | |-- pom.xml (JAR) > | ..... > |-- pluginN > |-- pom.xml (JAR) > {code} > NOTE: watch out for cyclic dependencies bwteen nutch-core and plugins, > introduce another POM to break the cycle if required. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)