Could you try and generate the pom.xml (see NUTCH-995<https://issues.apache.org/jira/browse/NUTCH-995>) and see if you are getting the same issues?
On 31 October 2011 16:41, lewis john mcgibbney <lewis.mcgibb...@gmail.com>wrote: > I think it's static Julien. This is where my concerns are. > > On Mon, Oct 31, 2011 at 4:38 PM, Julien Nioche < > lists.digitalpeb...@gmail.com> wrote: > >> >> >>> I was under the impression that to publish Nutch artefacts to maven repo >>> we need to have a working pom.xml? Is this correct? This was all I was >>> referring to. >>> >> >> OK, sorry I now understand >> >> yes we do. It should be generated automatically though (see >> NUTCH-995<https://issues.apache.org/jira/browse/NUTCH-995>). >> Is the pom.xml that gives you trouble generated or static? >> >> >> >>> >>> I'm not familiar with maven stuff so please correct where my outlook has >>> gaps. >>> >>> >>> On Mon, Oct 31, 2011 at 3:52 PM, Julien Nioche < >>> lists.digitalpeb...@gmail.com> wrote: >>> >>>> This is a bit different from my latest suggestion but also relevant : >>>> we can generate the POM from the IVY file. I still don't get why we are >>>> using Maven for building though >>>> >>>> >>>> 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 >>>> >>> >>> >>> >>> -- >>> *Lewis* >>> >>> >> >> >> -- >> * >> *Open Source Solutions for Text Engineering >> >> http://digitalpebble.blogspot.com/ >> http://www.digitalpebble.com >> > > > > -- > *Lewis* > > -- * *Open Source Solutions for Text Engineering http://digitalpebble.blogspot.com/ http://www.digitalpebble.com
