[
https://issues.apache.org/jira/browse/NUTCH-2292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15902538#comment-15902538
]
Thamme Gowda commented on NUTCH-2292:
-------------------------------------
[~lewismc] The reason for adding {{IntegrationTest.java}} was to group test
cases into Integration Tests.
My plan was to mark all the tests that require 'plugins.folders' as
IntegrationTest group.
Then exclude them from {{maven-surefire-plugin}} and run them after package
using {{maven-failsafe-plugin}}.
I was following this guide
http://www.javaworld.com/article/2074569/core-java/unit-and-integration-tests-with-maven-and-junit-categories.html
If you have found a way to get the plugin integration tests working, we can
delete it.
> 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)
