Menu
▾
▴
mockobjects-java-dev
|
From: Stefan B. <bo...@ap...> - 2004-02-03 07:20:30
|
On Mon, 02 Feb 2004, Nat Pryce <nat...@b1...> 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 |
|
From: Jeff M. <je...@cu...> - 2004-02-03 10:56:17
|
No please keep it in gump, we obviously need it there or we wouldn't be running around trying to fix things ;) I really don't see that five mails over five days is really a huge price to pay (Currently I'm getting 4000 a day courtesy of MyDoom) I've now removed a couple of dodge files Nat pointed me to so hopefully that's us sorted for a bit. On Tue, 2004-02-03 at 07:20, Stefan Bodewig wrote: > On Mon, 02 Feb 2004, Nat Pryce <nat...@b1...> > 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 > > > ------------------------------------------------------- > 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 -- Jeff Martin Memetic Engineer http://www.custommonkey.org/ |
|
From: Vincent M. <vm...@pi...> - 2004-02-03 22:17:34
|
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:bo...@ap...] > Sent: 03 February 2004 08:20 > To: gu...@ja... > Cc: mockobjects-java-dev > Subject: Re: [MO-java-dev] compilation problem for mockobjects > > On Mon, 02 Feb 2004, Nat Pryce <nat...@b1...> > 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: gum...@ja... > For additional commands, e-mail: gum...@ja... |
|
From: Stefan B. <bo...@ap...> - 2004-02-04 09:04:16
|
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.
|
|
From: Nat P. <nat...@b1...> - 2004-02-04 09:53:15
|
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
|
|
From: Stefan B. <bo...@ap...> - 2004-02-04 13:06:03
|
On Wed, 4 Feb 2004, Nat Pryce <nat...@b1...> 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 |
|
From: Nat P. <nat...@b1...> - 2004-02-04 15:47:54
|
On Wed, 2004-02-04 at 13:05, Stefan Bodewig wrote: > 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). I think the issue in this case is that some of the team added the project to gump and others did not know about it. So really, it's an internal communication and process issue that has brought to light the need to agree on how we use the HEAD branch. Which is a good thing. Another issue is how does Gump handle acceptance tests? A convention we are using on jmock is to allow failing acceptance tests into CVS to show what needs to be done long-term. The library itself and the unit tests will always compile and the unit tests will always pass, but the acceptance tests can fail or even not compile at all. Cheers, Nat. |
|
From: Nat P. <nat...@b1...> - 2004-02-04 15:49:08
|
Oops, I forgot to add my intended point to the last email. That is, perhaps gump output should be sent to a different list, mockobjects-gump for example. What do people think? Cheers, Nat. |
|
From: Jeff M. <je...@cu...> - 2004-02-04 16:03:45
|
I really don't see what the problem is. We've only had like 5 mails from gump in the last year it's not like we're inundated. Personally I think it's good for it to be as visible as possible, especially as our usual response seems to be not to fix the problem but demand that we stop getting mails. <joke> Man goes into a doctors and says "My arm hurts when I do this." the doctor replies "Don't do it then!" </joke> On Wed, 2004-02-04 at 15:48, Nat Pryce wrote: > Oops, I forgot to add my intended point to the last email. That is, > perhaps gump output should be sent to a different list, mockobjects-gump > for example. What do people think? > > Cheers, > Nat. > > > > > ------------------------------------------------------- > 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 -- Jeff Martin Memetic Engineer http://www.custommonkey.org/ |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X