David,
On Nov 23, 2006, at 10:44 AM, David Saff wrote:
My bad. I'll hope to have a fix in today.
Any word on this? A lot of projects in Gump depend on JUnit and the
nature of the system is such that local patches is not really
something we can do.
I have close to 350 projects that don'
I felt a disturbance in the gump, as if 354 projects cried out in
terror, and were suddenly silent.
Luckily, JUnit is now fixed.
David Saff
On 1/26/07, Gump Integration wrote:
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please vis
All,
I can't seem to replicate this locally. I have a feeling it has something
to do with updating the version to 4.4-snapshot-20070427-0047, but
everything works fine locally. Can someone else try a checkout and build?
Thanks,
David Saff
On 4/27/07, Gump Integration wrote:
To whom it ma
All,
The build script for JUnit should be working, but it depends on a new
jar that is in the CVS repository:
lib/hamcrest-core-1.1.jar
Can someone remind me how to tell gump about this? Thanks,
David Saff
-- Forwarded message --
From: Gump Integration
Date: Jul 10, 2007 3
I'm sorry: we had to switch our dependency back to hamcrest 1.1, which
I'm relatively sure has caused this problem. If someone can re-point
me to the 5-minute version of how to prevent this in the future, I can
try harder next time.
David Saff
-- Forwarded message --
From: Gu
I'm sorry: we had to switch our dependency back to hamcrest 1.1, which
I'm relatively sure has caused this problem. If someone can re-point
me to the 5-minute version of how to prevent this in the future, I can
try harder next time.
David Saff
I've changed the metadata for junit to point to th
I can't make out what the error is in this case. Can someone explain
further? Thanks,
David Saff
On Mon, Aug 17, 2009 at 5:06 AM, Gump
Integration wrote:
> To whom it may engage...
>
> This is an automated request, but not an unsolicited one. For
> more information please visit http://gump.a
