You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nutch.apache.org by "Lewis John McGibbney (JIRA)" <ji...@apache.org> on 2013/01/14 01:42:12 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=13552365#comment-13552365 ] 

Lewis John McGibbney commented on NUTCH-1371:
---------------------------------------------

Hi Julien. So what is the plan here? I know that this patch is just a start. 
It does not take into consideration the plugin dependencies which I suppose should also be managed via Maven. In addition, the ivy directory should ideally be removed. The maven-ant-tasks jar can then be added to out lib directory.
                
> 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
>            Reporter: Julien Nioche
>             Fix For: 1.7, 2.2
>
>         Attachments: 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira