nutch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julien Nioche (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (NUTCH-1371) Replace Ivy with Maven Ant tasks
Date Tue, 04 Feb 2014 12:40:11 GMT

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

Julien Nioche commented on NUTCH-1371:
--------------------------------------

Hi Talat

bq. Actually I have some problems with ant+ivy style. Firstly, when I change a configuration
file I always have to run ant runtime target.

that has nothing to do with Ant+ivy itself. It is just that you need to rebuild the runtime
environments if you want the content of conf to be there. You can edit the content of runtime/local/conf
directly if you want your changes to be operational without recompiling

bq.  In addition to this, When I change a build dependency, I always have to run ant eclipse
target for working on the IDE. At the present dependencies are managed from the built files.
I think when we migrate maven, they will be solved. How do you solve this type of problems
?

use IvyDE in Eclipse. it will use the ivy deps file in the same way as the Maven plugin does


> 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-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.1.5#6160)

Mime
View raw message