nutch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Talat UYARER (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (NUTCH-1371) Replace Ivy with Maven Ant tasks
Date Tue, 07 Jan 2014 12:47:51 GMT

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

Talat UYARER commented on NUTCH-1371:
-------------------------------------

Hi [~lewismc],

Different from the [~jnioche]'s suggestion, I want to learn why do we 'not' migrate Nutch
completely as Maven project ? If it wont be a problem to migrate completely, I am volunteer
to do it.

> 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.8, 2.4
>
>         Attachments: 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.1.5#6160)

Mime
View raw message