[
https://issues.apache.org/jira/browse/NUTCH-995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13044581#comment-13044581
]
Chris A. Mattmann commented on NUTCH-995:
-----------------------------------------
bq. Sure, it's just a wish for standards (cross-apache too). It also helps
ctrl+F people looking for 'maven' and 'pom' in the build script.
The naming of Ant targets is not something I would imagine would be
standardized -- and if so -- you've arrived at Maven :-)
bq. I as a nutch consumer wasn't really concerned with pushing to Central. I'm
concerned about 'consuming' Nutch with a mvn install
And as noted above, it looks like we have a workaround for that. What's
stopping you from doing:
{code:xml}
<dependency>
<groupId>org.apache.nutch</groupId>
<artifactId>nutch</artifactId>
<version>1.3</version>
<exclusions>
<exclusion>
<groupId>com.sun.jdmk</groupId>
<artifactId>jmxtools</artifactId>
</exclusion>
<exclusion>
<groupId>com.sun.jmx</groupId>
<artifactId>jmxri</artifactId>
</exclusion>
</dependency>
{code}
> 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
