[ 
https://issues.apache.org/jira/browse/NUTCH-995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13044605#comment-13044605
 ] 

Mattmann, Chris A (388J) commented on NUTCH-995:
------------------------------------------------

Hi Gabriele,



Well, that's the point they won't have to run ant release/deploy ; mvn install. 
If the jars are up on Central, you simply include Nutch as a Maven dependency 
in your project and you're OK, Maven will download them for you. There's no 
need to run mvn install. 


We can simply put it up on the Wiki -- aka create a page: How do I use Nutch in 
a Maven project?


I'd rather not use Maven as a rationale to downgrade a dependency. That seems 
to be a little brittle to me.


They don't belong in mvn.template -- they belong in whatever project you're 
trying to include Nutch in as a Maven dependency, along with the Nutch JAR 
dependency block like I pasted.

Cheers,
Chris


++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: [email protected]
WWW:   http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++



> 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

Reply via email to