[
https://issues.apache.org/jira/browse/NUTCH-2292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17153725#comment-17153725
]
Sebastian Nagel commented on NUTCH-2292:
----------------------------------------
Hi [~balaShashanka], I fear that merging the existing branch is more work than
taking the approaches and some fragments from the first run and starting anew.
Parts can be automatized, eg. converting dependencies via
[makepom|https://ant.apache.org/ivy/history/2.5.0/use/makepom.html].
Yes, it's a good idea to split this into sub-tasks. However, at any point in
development we need a build system which is able to build the runtime. I
haven't verified it, but maybe it's possible to keep the existing directory
structure also using Maven. This would help to upkeep work on the source code
and keeps all patches/PRs mergable.
> 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
> Labels: gsoc2019
> Fix For: 1.18
>
>
> 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
(v8.3.4#803005)
