Hi Chris Yah, I'm trying to get it working so that we have a working pom that we can > release to Maven Central (we need a POM to be working > in order to run the mvn release plugin which is what I run to publish to > repository.apache.org and then sync to Central). >
yep > > Nutch is an interesting case where we've got folks actively developing > that know Ant+Ivy, and then folks who are actively developing > and know Maven. If there are folks that are willing to put in the work to > maintain both sides, I don't see a harm to maintaining both. > If the pom falls out of sync and is like 2 versions behind; or if the same > goes for the Ivy build, then it's time to start discussing retiring > one or the other I think. But, for me, since we've decided it's a good > thing as a community to have Nutch in Maven Central, to me each time > I roll the RC I need to get the pom working. > sure we definitely need the pom.xml for publishing having said that does anywone have a rough idea of how complicated it would be to use ANT+MAVEN tasks instead of ANT+IVY? I listed some of the advantages earlier and a few more come to mind (e.g. better integration in Eclipse etc...) Any feedback on using ANT+MAVEN at all? Jul > > Thanks! > > Cheers, > Chris > > > > > On 31 October 2011 15:39, Markus Jelsma <markus.jel...@openindex.io> > wrote: > > This was the thing, isn't it? > > https://issues.apache.org/jira/browse/NUTCH-995 > > > > On Monday 31 October 2011 16:28:18 Julien Nioche wrote: > > > Guys, > > > > > > I have probably missed a discussion on this lately but I really don't > > > remember that we'd decided to move from ANT+IVY. We've had numerous > > > discussions on this in the past, all leading to the conclusion that > > > maintaining two systems is a bad idea. > > > > > > Have I missed something? > > > > > > Jul > > > > > > PS: If we had to change something, I'd rather go for ANT+MAVEN tasks > and > > > use a single pom.xml for managing the dependencies and declaring our > > > artefacts when publishing but keep the flexibility of ANT (plus the > fact > > > that we can keep our ANT tasks). > > > > > > On 31 October 2011 15:14, Mattmann, Chris A (388J) < > > > > > > chris.a.mattm...@jpl.nasa.gov> wrote: > > > > Guys, I'm working on this right now as part of the RC, so hopefully > > > > should have a working > > > > Maven build soonish... > > > > > > > > Cheers, > > > > Chris > > > > > > > > On Oct 31, 2011, at 8:12 AM, lewis john mcgibbney wrote: > > > > > I suppose they probably could Markus. I'm not going to have time to > > > > > > > > check them today but will try and experiment locally tomorrow maybe. > I > > > > have a feeling that they're required rather than to0 be excluded. or > > > > maybe I'm reading the console output incorrectly. > > > > > > > > > On Mon, Oct 31, 2011 at 1:09 PM, Markus Jelsma < > > > > > > > > markus.jel...@openindex.io> wrote: > > > > > Can't those deps be excluded just like in our ivy.xml? > > > > > > > > > > On Monday 31 October 2011 14:05:35 lewis john mcgibbney wrote: > > > > > > Hi Everyone, > > > > > > > > > > > > I just ran the maven build on our trunk code, the output of > which can > > > > > > > > be > > > > > > > > > > seen here [1]. > > > > > > > > > > > > There are some unresolved dependencies which I think fail the > build. > > > > > > I thought this might be useful for anyone dealing with pom.xml > files > > > > > > in > > > > > > > > the > > > > > > > > > > near future. I'm going to disable the build again for the time > being. > > > > > > > > > > > > Thanks > > > > > > > > > > > > Lewis > > > > > > > > > > > > [1] > > > > > > > > > https://builds.apache.org/view/M-R/view/Nutch/job/nutch-trunk-maven/3/con > > > > so > > > > > > > > > > le > > > > > > > > > > -- > > > > > Markus Jelsma - CTO - Openindex > > > > > http://www.linkedin.com/in/markus17 > > > > > 050-8536620 / 06-50258350 > > > > > > > > > > > > > > > > > > > > -- > > > > > Lewis > > > > > > > > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > > > > Chris Mattmann, Ph.D. > > > > Senior Computer Scientist > > > > NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA > > > > Office: 171-266B, Mailstop: 171-246 > > > > Email: chris.a.mattm...@nasa.gov > > > > WWW: http://sunset.usc.edu/~mattmann/ > > > > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > > > > Adjunct Assistant Professor, Computer Science Department > > > > University of Southern California, Los Angeles, CA 90089 USA > > > > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > > > > -- > > 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: chris.a.mattm...@nasa.gov > WWW: http://sunset.usc.edu/~mattmann/ > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > Adjunct Assistant Professor, Computer Science Department > University of Southern California, Los Angeles, CA 90089 USA > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > > -- * *Open Source Solutions for Text Engineering http://digitalpebble.blogspot.com/ http://www.digitalpebble.com
