[
https://issues.apache.org/jira/browse/NUTCH-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julien Nioche updated NUTCH-1371:
---------------------------------
Attachment: NUTCH-1371-plugins.trunk.patch
Path which allows using pom.xml to declare the dependencies for plugins. I have
given an example for parse-tika. If a plugin contains a pom.xml file then it
will use Maven for resolving the dependencies, otherwise it will rely on Ivy.
This should help transitioning progressively.
We could have a super-pom in the plugins/dir so that common elements are
defined there.
Remember to add maven-ant-tasks-2.1.3.jar to the ivy dir.
NOTE: WE WILL STILL USE ANT FOR BUILDING NUTCH. What this patch does is that
it removes the need for Ivy and simplifies the setup as we won't need to keep
the pom.xml and the ivy.xml files in sync.
> 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: 2.4
>
> Attachments: NUTCH-1371.patch, NUTCH-1371-plugins.trunk.patch,
> NUTCH-1371-pom.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 was sent by Atlassian JIRA
(v6.1#6144)
