[
https://issues.apache.org/jira/browse/NUTCH-821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Enis Soztutar updated NUTCH-821:
--------------------------------
Attachment: nutchbase-ivy_v1.patch
I'm attaching a patch which introduces ivy to nutch builds. It is a patch
against current nutchbase code base hosted at github.
We can adopt this patch to current nutch trunk, but I see little point in doing
so since the two code bases will merge eventually.
The way ivy patch works is as follows :
There are two configurations default and test. Test dependencies are managed at
test configuration.
libraries not managed by ivy are still at their old locations ( for example
"nutch/lib/" or "nutch/src/plugin/clustering-carrot/lib/")
the root ivy file is located at nutch/ivy/ivy.xml
Each plugin has it's own ivy file, which is located at
nutch/src/plugin/<plugin>/ivy.xml
root dependencies are downloaded to build/lib
plugin dependencies are downloaded to build/plugins/<plugin>/
I have upgraded some of the libraries in the process, where only a the release
number changed only in minor number (for example lucene-core-2.4.0 -> 2.4.1 )
> Use ivy in nutch builds
> -----------------------
>
> Key: NUTCH-821
> URL: https://issues.apache.org/jira/browse/NUTCH-821
> Project: Nutch
> Issue Type: New Feature
> Components: build
> Affects Versions: 2.0
> Reporter: Enis Soztutar
> Assignee: Enis Soztutar
> Fix For: 2.0
>
> Attachments: nutchbase-ivy_v1.patch
>
>
> Ivy is the de-facto dependency management tool used in conjunction with Ant.
> It would be nice if we switch to using Ivy in Nutch builds.
> Maven is also an alternative, but I think Nutch will benefit more with an
> Ant+Ivy architecture.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
