Re: Nutch Maven build

2011-10-31 Thread lewis john mcgibbney 
I'm also a bit hesitant to be mucking around with this using ant tasks such
as deploy and release etc. Its not my intention to start shipping this
stuff off to maven central.
Can you please give a brief run-down of how this is meant to work. I get it
at conceptual level however have never seen it working.

On Mon, Oct 31, 2011 at 5:31 PM, lewis john mcgibbney <
lewis.mcgibb...@gmail.com> wrote:

> OK I'm getting similar problems to what Gabriele was getting when he was
> working with you guys on this one.
>
> I need more time to properly look through the correspondence, as well as
> the code in more detail before I am able to move on with this one.
>
> BUILD FAILED
> /home/lewis/ASF/trunk/build.xml:216: Problem: failed to create task or
> type antlib:org.apache.maven.artifact.ant:mvn
> Cause: The name is undefined.
> Action: Check the spelling.
> Action: Check that any custom tasks/types have been declared.
> Action: Check that any / declarations have taken
> place.
> No types or tasks have been defined in this namespace yet
>
> This appears to be an antlib declaration.
> Action: Check that the implementing library exists in one of:
> -/usr/share/ant/lib
> -/home/lewis/.ant/lib
> -a directory added on the command line with the -lib argument
>
>
> Total time: 21 seconds
>
>
>
> On Mon, Oct 31, 2011 at 4:44 PM, Julien Nioche <
> lists.digitalpeb...@gmail.com> wrote:
>
>> Could you try and generate the pom.xml (see 
>> NUTCH-995)
>> and see if you are getting the same issues?
>>
>>
>


-- 
*Lewis*

Re: Nutch Maven build

2011-10-31 Thread lewis john mcgibbney 
OK I'm getting similar problems to what Gabriele was getting when he was
working with you guys on this one.

I need more time to properly look through the correspondence, as well as
the code in more detail before I am able to move on with this one.

BUILD FAILED
/home/lewis/ASF/trunk/build.xml:216: Problem: failed to create task or type
antlib:org.apache.maven.artifact.ant:mvn
Cause: The name is undefined.
Action: Check the spelling.
Action: Check that any custom tasks/types have been declared.
Action: Check that any / declarations have taken place.
No types or tasks have been defined in this namespace yet

This appears to be an antlib declaration.
Action: Check that the implementing library exists in one of:
-/usr/share/ant/lib
-/home/lewis/.ant/lib
-a directory added on the command line with the -lib argument


Total time: 21 seconds


On Mon, Oct 31, 2011 at 4:44 PM, Julien Nioche <
lists.digitalpeb...@gmail.com> wrote:

> Could you try and generate the pom.xml (see 
> NUTCH-995)
> and see if you are getting the same issues?
>
>

Re: Nutch Maven build

2011-10-31 Thread Julien Nioche 
Could you try and generate the pom.xml (see
NUTCH-995)
and see if you are getting the same issues?

On 31 October 2011 16:41, lewis john mcgibbney 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).
>> 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 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

>>>
>>>
>>>
>>> -

Re: Nutch Maven build

2011-10-31 Thread lewis john mcgibbney 
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).
> 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 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*

Re: Nutch Maven build

2011-10-31 Thread Julien Nioche 
>
> 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).
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 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

Re: Nutch Maven build

2011-10-31 Thread Mattmann, Chris A (388J) 
Hey Julien,

On Oct 31, 2011, at 8:52 AM, Julien Nioche 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

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). 

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.

Thanks!

Cheers,
Chris

> 
> On 31 October 2011 15:39, Markus Jelsma  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
++

Re: Nutch Maven build

2011-10-31 Thread lewis john mcgibbney 
Hi Julien,

You are correct, as far as I'm aware we're sticking to the Ant/Ivy config.
I think it works excellently for Nutch, especially for testing.

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.

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 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*

Re: Nutch Maven build

2011-10-31 Thread Julien Nioche 
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  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

Re: Nutch Maven build

2011-10-31 Thread Markus Jelsma 
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

Re: Nutch Maven build

2011-10-31 Thread Julien Nioche 
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/conso
> > > 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
> ++
>
>


-- 
*
*Open Source Solutions for Text Engineering

http://digitalpebble.blogspot.com/
http://www.digitalpebble.com

Re: Nutch Maven build

2011-10-31 Thread Mattmann, Chris A (388J) 
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  
> 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/conso
> > 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
++

Re: Nutch Maven build

2011-10-31 Thread lewis john mcgibbney 
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
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/conso
> > le
>
> --
> Markus Jelsma - CTO - Openindex
> http://www.linkedin.com/in/markus17
> 050-8536620 / 06-50258350
>



-- 
*Lewis*

Re: Nutch Maven build

2011-10-31 Thread Markus Jelsma 
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/conso
> le

-- 
Markus Jelsma - CTO - Openindex
http://www.linkedin.com/in/markus17
050-8536620 / 06-50258350