[
https://issues.apache.org/jira/browse/NUTCH-995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13044342#comment-13044342
]
Julien Nioche commented on NUTCH-995:
-------------------------------------
@Chris : could be due to recent changes on the build file. The issue can be
solved by simply specify 2.2.0 in the conf file and use 'ant -lib ivy ....' to
force it to load the one we want. I haven't found how to get ANT/IVY to use the
version we specify instead of relying on the one in the ANT local install -
which in many cases is 2.1.0.
We could also add the Maven task jar in the same lib to facilitate the second
part of the publishing but it is less important as this is typically done only
once by the person pushing the release.
> Generate POM file using the Ivy makepom task
> ---------------------------------------------
>
> Key: NUTCH-995
> URL: https://issues.apache.org/jira/browse/NUTCH-995
> Project: Nutch
> Issue Type: Improvement
> Reporter: Julien Nioche
> Assignee: Chris A. Mattmann
> Fix For: 1.3
>
> Attachments: NUTCH-955-1.3.patch, NUTCH-997.branch-1.3.v2.patch,
> mvn-template-build.patch
>
>
> We currently have a pom.xml file in the SVN repository and use it for
> publishing our artefacts. The trouble with this is that we need to keep its
> content in sync with our ivy file. Instead we could use the makepom task
> (http://ant.apache.org/ivy/history/2.2.0/use/makepom.html) to generate the
> pom.xml automatically.
> The existing pom.xml for 1.3 needs fixing anyway as it declares dependencies
> to GORA and has the wrong versions for some dependencies.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
