Re: [MO-java-dev] compilation problem for mockobjects

[Nat P. <nat...@b1...>]

Considering what Gump is meant to be used for, would it be better for it to
be "edge triggered" rather than "level triggered".  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?

Cheers,
            Nat.
_______________________
Dr. Nathaniel Pryce
B13media Ltd.
http://www.b13media.com
+44 (0)7712 526 661

----- Original Message -----
From: "Stefan Bodewig" <bo...@ap...>
To: <gu...@ja...>
Cc: <moc...@li...>
Sent: Wednesday, February 04, 2004 9:04 AM
Subject: Re: [MO-java-dev] compilation problem for mockobjects


> On Tue, 3 Feb 2004, Vincent Massol <vm...@pi...> 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.
>
>
>
> -------------------------------------------------------
> The SF.Net email is sponsored by EclipseCon 2004
> Premiere Conference on Open Tools Development and Integration
> See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
> http://www.eclipsecon.org/osdn
> _______________________________________________
> Mockobjects-java-dev mailing list
> Moc...@li...
> https://lists.sourceforge.net/lists/listinfo/mockobjects-java-dev