You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@gump.apache.org by Antoine Lévy-Lambert <an...@antbuild.com> on 2004/02/02 18:13:26 UTC
[Fwd: Re: [MO-java-dev] compilation problem for mockobjects]
This email did not seem to make its way yet into the gump list.
Antoine
-------- Original Message --------
Subject: Re: [MO-java-dev] compilation problem for mockobjects
Date: 02 Feb 2004 15:33:15 +0000
From: Nat Pryce <na...@b13media.com>
To: Antoine Lévy-Lambert <an...@antbuild.com>
CC: jakarta-gump list <gu...@jakarta.apache.org>, mockobjects-java-dev
<mo...@lists.sourceforge.net>
References: <40...@antbuild.com>
<40...@m3p.co.uk> <40...@antbuild.com>
<40...@m3p.co.uk> <40...@antbuild.com>
<10...@plasma.doc.ic.ac.uk>
<40...@antbuild.com>
Who put mockobjects.com into gump? Whoever it is, they should sort out
the problem.
Cheers,
Nat.
On Mon, 2004-02-02 at 15:18, Antoine Lévy-Lambert wrote:
> Nat Pryce wrote:
>
> >The cause of the problem is that Gump is pulling the head revision from
> >CVS, which is where refactoring and experimental development happens,
> >instead of a tagged release which has been tested. Configure Gump to
> >pull version 0.09 out of CVS and it will build fine.
> >
> >Cheers,
> > Nat.
> >
> >On Mon, 2004-02-02 at 13:43, Antoine Lévy-Lambert wrote:
> >
> >
> >>Steve Freeman wrote:
> >>
> >>
> >>
> >>>We're investigating, since someone else did the gump configuration and
> >>>I don't actually know what's involved. A bit tricky since I'm away on
> >>>site at the moment.
> >>>
> >>>S.
> >>>
> >>>Antoine Lévy-Lambert wrote:
> >>>
> >>>
> >>>
> >>>>Hi Steve,
> >>>>
> >>>>do you think you will be able to fix mockobjects so that it compiles
> >>>>on gump soon ?
> >>>>
> >>>>I need mockobjects because it is an indirect dependency of
> >>>>ant-xdocs-proposals.
> >>>>
> >>>>A lot of other projects are dependent upon mockobjects.
> >>>>
> >>>>Cheers,
> >>>>
> >>>>Antoine
> >>>>
> >>>>
> >>>>
> >>For me the failure does not seem related to Gump :
> >>
> >>core.test.mockobjects.dynamic.InvocationMatcherTest
> >>
> >>this class does not compile because it tries to use the
> >>internal class
> >>com.mockobjects.dynamic.InvocationMatcher.Arguments
> >>which was suppressed on the 29th of October :
> >>http://cvs.sourceforge.net/viewcvs.py/mockobjects/mockobjects-java/src/core/com/mockobjects/dynamic/InvocationMatcher.java?r1=1.3&r2=1.4
> >>
> >>Antoine
> >>
> >>
> >>
> >>
> >>
> >
> >
> Hi,
>
> gump's job is really to test head revisions., and to test that the head
> revisions of the participant projects are compatible with one another.
>
> If mockobjects is going to be in a state where it does not build for a
> long time, then we can make some projects in gump dependent upon a
> packaged version of mockobjects.
>
>
> Antoine
Re: [MO-java-dev] compilation problem for mockobjects
Posted by Stefan Bodewig <bo...@apache.org>.
On Wed, 4 Feb 2004, Nat Pryce <na...@b13media.com> wrote:
> Considering what Gump is meant to be used for, would it be better
> for it to be "edge triggered" rather than "level triggered".
It depends on the community you want to reach. Sometimes it takes
repeated nagging to get the message through. Sometimes you generate
the opposite effect by nagging, i.e. mails get ignored.
> That is, should it send a message when a project fails to build, and
> then sends a message when the project builds successfully again,
> instead of sending a message every time it fails to build a broken
> project?
Yes, this would certainly be an option, and I think much of the
statistics sthe new Python implementation of Gump collects can be used
for that. We also generate RSS feeds that contain exactly these types
of status changes IIRC.
The email based nagging system has been Gump's traditional approach
and it has done an outstanding job in many cases. I agree that it is
plain annoying if it comes unwanted.
Maybe we can improve the nagging part in the Python implementation to
be configurable on a project level. Some projects may want a nightly
report even on successful builds as confirmation, others may only want
to get notified on status changes (as you describe it).
Stefan
Re: [MO-java-dev] compilation problem for mockobjects
Posted by Stefan Bodewig <bo...@apache.org>.
On Tue, 3 Feb 2004, Vincent Massol <vm...@pivolis.com> wrote:
> I haven't been following the discussion but for the record I think
> using Gump is great and should be continued.
I've seen a similar comment by Jeff in the archives (I tried to
subscribe to mockobjects-java-dev but SF's mailing list manager was
down yesterday, so I'm not yet subscribed).
What I've done so far is that I've added mockobjects-0.09 and made all
projects in Gump depend on that. Gump still tries to build the CVS
HEAD revisions of mockobjects[1][2], but no other project depends on
it and I've turned of nagging.
Cheers
Stefan
Footnotes:
[1] http://gump.covalent.net/log/mockobjects-cvs-head.html
[2] it currently doesn't work in the new Python version, but we'll
work on it.
RE: [MO-java-dev] compilation problem for mockobjects
Posted by Vincent Massol <vm...@pivolis.com>.
I haven't been following the discussion but for the record I think using
Gump is great and should be continued. That said, I'm no longer active
on the mockobjects project so I'll let active members decide on this.
Thanks
-Vincent
PS: Stefan, I do really appreciate Gump and as soon as I find a few
minutes I'll continue working towards helping make the cactus build work
with Gumpy.
> -----Original Message-----
> From: Stefan Bodewig [mailto:bodewig@apache.org]
> Sent: 03 February 2004 08:20
> To: gump@jakarta.apache.org
> Cc: mockobjects-java-dev
> Subject: Re: [MO-java-dev] compilation problem for mockobjects
>
> On Mon, 02 Feb 2004, Nat Pryce <na...@b13media.com>
> wrote:
>
> > Who put mockobjects.com into gump? Whoever it is, they should sort
> > out the problem.
>
> Oh my.
>
> Having mockobjects built by Gump used to be appreciated by Jeff and
> Vincent. Given that cactus relies on mockobjects and also relies on
> Gump quite a bit, this seemed natural.
>
> There is no problem with removing mockobjects from Gump if that is
> what you want. I'll take care of it.
>
> Cheers
>
> Stefan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: gump-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: gump-help@jakarta.apache.org
Re: [MO-java-dev] compilation problem for mockobjects
Posted by Stefan Bodewig <bo...@apache.org>.
On Mon, 02 Feb 2004, Nat Pryce <na...@b13media.com>
wrote:
> Who put mockobjects.com into gump? Whoever it is, they should sort
> out the problem.
Oh my.
Having mockobjects built by Gump used to be appreciated by Jeff and
Vincent. Given that cactus relies on mockobjects and also relies on
Gump quite a bit, this seemed natural.
There is no problem with removing mockobjects from Gump if that is
what you want. I'll take care of it.
Cheers
Stefan