hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From James Abley <james.ab...@gmail.com>
Subject Re: Continuum build failures
Date Sun, 13 Sep 2009 06:02:57 GMT
2009/9/13 sebb <sebbaz@gmail.com>

> On 12/09/2009, sebb <sebbaz@gmail.com> wrote:
> > On 12/09/2009, sebb <sebbaz@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
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message