You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by sebb <se...@gmail.com> on 2009/09/12 14:37:23 UTC
Continuum build failures
I've been unable to fix the Continuum build failures; I think this may
be because the parent pom (which now defines the clover2 version) is
not being updated in the local repo.
I'm going to try the following, which I'll revert as necessary:
Adding the clover2 version to the core POM
If that does not work, I'll try to see if Continuum will build
everything starting at the parent.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org
Re: Continuum build failures
Posted by Oleg Kalnichevski <ol...@apache.org>.
James Abley wrote:
> 2009/9/13 sebb <se...@gmail.com>
>
>> On 12/09/2009, sebb <se...@gmail.com> wrote:
>>> On 12/09/2009, sebb <se...@gmail.com> wrote:
>>> > I've been unable to fix the Continuum build failures; I think this may
>>> > be because the parent pom (which now defines the clover2 version) is
>>> > not being updated in the local repo.
>>> >
>>> > I'm going to try the following, which I'll revert as necessary:
>>> >
>>> > Adding the clover2 version to the core POM
>>>
>>>
>>> That worked.
>>>
>>> So it looks like the problem is that the parent POM is not being
>>> updated in the repo.
>>>
>>>
>>> > If that does not work, I'll try to see if Continuum will build
>>> > everything starting at the parent.
>>>
>>>
>>> I'm going to try adding the parent as a project.
>>>
>> Continuum fails to add the parent as a multi-module project. Not sure
>> why; just reports a generic failure message.
>>
>> So added the parent project as a standalone.
>> It then failed to build as it cannot find the modules.
>>
>> Eventually realised that if parent project is built with the -N
>> (non-recursive) option it won't care about the modules; this worked
>> and now core and client seem to build OK.
>>
>> There does not seem to be any way to tell Continuum to build the
>> projects in a particular order, so changes to the parent pom may take
>> a couple of builds to be seen by the modules.
>>
>
> That's why we switched to Hudson internally, but I guess there may be
> political reasons as well as operations overhead here!
>
>
We have been using Hudson for quite some time now in parallel to
Continuum. It has been working really great most of the time. That is
the reason why I did not feel there was any urgency in fixing Continuum.
Many thanks to Sebastian for looking into the issue and fixing the
build, nonetheless.
http://hudson.zones.apache.org/hudson/view/HttpComponents/
Cheers
Oleg
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
>> For additional commands, e-mail: dev-help@hc.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org
Re: Continuum build failures
Posted by James Abley <ja...@gmail.com>.
2009/9/13 sebb <se...@gmail.com>
> On 12/09/2009, sebb <se...@gmail.com> wrote:
> > On 12/09/2009, sebb <se...@gmail.com> wrote:
> > > I've been unable to fix the Continuum build failures; I think this may
> > > be because the parent pom (which now defines the clover2 version) is
> > > not being updated in the local repo.
> > >
> > > I'm going to try the following, which I'll revert as necessary:
> > >
> > > Adding the clover2 version to the core POM
> >
> >
> > That worked.
> >
> > So it looks like the problem is that the parent POM is not being
> > updated in the repo.
> >
> >
> > > If that does not work, I'll try to see if Continuum will build
> > > everything starting at the parent.
> >
> >
> > I'm going to try adding the parent as a project.
> >
>
> Continuum fails to add the parent as a multi-module project. Not sure
> why; just reports a generic failure message.
>
> So added the parent project as a standalone.
> It then failed to build as it cannot find the modules.
>
> Eventually realised that if parent project is built with the -N
> (non-recursive) option it won't care about the modules; this worked
> and now core and client seem to build OK.
>
> There does not seem to be any way to tell Continuum to build the
> projects in a particular order, so changes to the parent pom may take
> a couple of builds to be seen by the modules.
>
That's why we switched to Hudson internally, but I guess there may be
political reasons as well as operations overhead here!
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
> For additional commands, e-mail: dev-help@hc.apache.org
>
>
Re: Continuum build failures
Posted by sebb <se...@gmail.com>.
On 12/09/2009, sebb <se...@gmail.com> wrote:
> On 12/09/2009, sebb <se...@gmail.com> wrote:
> > I've been unable to fix the Continuum build failures; I think this may
> > be because the parent pom (which now defines the clover2 version) is
> > not being updated in the local repo.
> >
> > I'm going to try the following, which I'll revert as necessary:
> >
> > Adding the clover2 version to the core POM
>
>
> That worked.
>
> So it looks like the problem is that the parent POM is not being
> updated in the repo.
>
>
> > If that does not work, I'll try to see if Continuum will build
> > everything starting at the parent.
>
>
> I'm going to try adding the parent as a project.
>
Continuum fails to add the parent as a multi-module project. Not sure
why; just reports a generic failure message.
So added the parent project as a standalone.
It then failed to build as it cannot find the modules.
Eventually realised that if parent project is built with the -N
(non-recursive) option it won't care about the modules; this worked
and now core and client seem to build OK.
There does not seem to be any way to tell Continuum to build the
projects in a particular order, so changes to the parent pom may take
a couple of builds to be seen by the modules.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org
Re: Continuum build failures
Posted by sebb <se...@gmail.com>.
On 12/09/2009, sebb <se...@gmail.com> wrote:
> I've been unable to fix the Continuum build failures; I think this may
> be because the parent pom (which now defines the clover2 version) is
> not being updated in the local repo.
>
> I'm going to try the following, which I'll revert as necessary:
>
> Adding the clover2 version to the core POM
That worked.
So it looks like the problem is that the parent POM is not being
updated in the repo.
> If that does not work, I'll try to see if Continuum will build
> everything starting at the parent.
I'm going to try adding the parent as a project.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org