+1 to automagically generating it if we can! :) I baked it up to publish Nutch to Maven Central (which is a release manager task) but would be happy to have it auto generated.
Cheers, Chris On Apr 12, 2011, at 7:24 AM, Julien Nioche wrote: > Someone suggested that we used an ant task to generate the pom from the Ivy > files. This would be far a cleaner option then having to keep this bl***d > pom.xml file in sync all the time > > On 12 April 2011 15:11, Markus Jelsma <[email protected]> wrote: > Hi guys, > > I found out that pom.xml lists older dependency versions and some unused > dependencies in both trunk and 1.3-dev. In case of 1.3 i believe Jetty and > Lucene can be removed as depenency. Not sure about Jetty in trunk due to the > webapp. > > At least i messed up with versions for NUTCH-980 and someone fixed the wrong > version for Xerces and Tika is still behind. Didn't spot upgrading pom.xml on > the dev wiki. > > Must a ticket be created for updating pom.xml? At least the wiki should be > updated to pay attention to pom when updating dependencies ;) > > Cheers, > -- > Markus Jelsma - CTO - Openindex > http://www.linkedin.com/in/markus17 > 050-8536620 / 06-50258350 > > > > -- > > Open Source Solutions for Text Engineering > > http://digitalpebble.blogspot.com/ > http://www.digitalpebble.com ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 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 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
