You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nutch.apache.org by "Viacheslav Dobromyslov (JIRA)" <ji...@apache.org> on 2014/09/23 12:18:34 UTC

[jira] [Commented] (NUTCH-1371) Replace Ivy with Maven Ant tasks

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

Viacheslav Dobromyslov commented on NUTCH-1371:
-----------------------------------------------

It's my dream to be able to build Nutch with Maven.


> Replace Ivy with Maven Ant tasks
> --------------------------------
>
>                 Key: NUTCH-1371
>                 URL: https://issues.apache.org/jira/browse/NUTCH-1371
>             Project: Nutch
>          Issue Type: Improvement
>          Components: build
>    Affects Versions: 1.7, 2.2.1
>            Reporter: Julien Nioche
>            Assignee: Lewis John McGibbney
>             Fix For: 1.10
>
>         Attachments: NUTCH-1371-2x.patch, NUTCH-1371-plugins.trunk.patch, NUTCH-1371-pom.patch, NUTCH-1371-r1461140.patch, NUTCH-1371.patch
>
>
> We might move to Maven altogether but a good intermediate step could be to rely on the maven ant tasks for managing the dependencies. Ivy does a good job but we need to have a pom file anyway for publishing the artefacts which means keeping the pom.xml and ivy.xml contents in sync. Most devs are also more familiar with Maven, and it is well integrated in IDEs. Going the ANT+MVN way also means that we don't have to rewrite the whole building process and can rely on our existing script



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)