[
https://issues.apache.org/jira/browse/NUTCH-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13614414#comment-13614414
]
Lewis John McGibbney edited comment on NUTCH-1371 at 3/26/13 6:39 PM:
----------------------------------------------------------------------
Hi Roland. I think the ivy directory should be removed here?
Additionally there are other discrepancies here such as the accuracy of pom.xml
for truly reflecting an accurate representation of current ivy.xml (including
exclusions, etc).
Finally, every plugin needs to be addressed does they not?
Thank you very much for the patch Roland.
was (Author: lewismc):
Hi Roland. I think the ivy directory should be removed here?
Additionally there are other discrepancies here such as the accuracy of pom.xml
for truly reflecting an accurate representation of current ivy.xml (including
exclusions, etc).
Finally, every plugin needs to be addressed does they not?
> 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
> Assignee: Lewis John McGibbney
> Fix For: 1.7, 2.2
>
> Attachments: NUTCH-1371.patch, NUTCH-1371-r1461140.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
