[ 
https://issues.apache.org/jira/browse/NUTCH-2292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15901920#comment-15901920
 ] 

Thamme Gowda commented on NUTCH-2292:
-------------------------------------

[~lewismc] Yes I saw that printed in log but the  test was not marked as 
failure in {{TestOutlinkExtractor}}. 
{noformat}
$ cat 
nutch-core/target/surefire-reports/org.apache.nutch.parse.TestOutlinkExtractor.txt
-------------------------------------------------------------------------------
Test set: org.apache.nutch.parse.TestOutlinkExtractor
-------------------------------------------------------------------------------
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.015 sec - in 
org.apache.nutch.parse.TestOutlinkExtractor
{noformat}

 There was a JVM crash (possibly due to a System.exit()) in some other test 
case which I am unable to recollect. I will re run and post you

> 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
>             Fix For: 1.13
>
>
> 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
(v6.3.15#6346)

Reply via email to