To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project packaged-jmock has an issue affecting its community integration.
This issue
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project packaged-jmock has an issue affecting its community integration.
This issue
Von: Gump general_at_gump.apache.org
Datum: Thu, 19 Jan 2006 00:03:53 PST
Project packaged-jmock has an issue affecting its community integration.
This issue affects 147 projects,
and has been outstanding for 2 runs.
I wonder why so many projects depend on *our* packaged jmock. At least
On Thu, 19 Jan 2006, Jörg Heinicke [EMAIL PROTECTED] wrote:
I wonder why so many projects depend on *our* packaged jmock.
Ahh, for historical reasons.
I was experimenting with building jmock and it simply will never work
(a backwards incomatible change in JUnit in the dead 3.8.x branch made
On 19.01.2006 14:59, Carsten Ziegeler wrote:
Isn't the gump descriptor currently totally useless as it
is based on the old directory structure?
Maybe we should fix it ;) Seriously ... how do other Maven projects get
built with gump?
Jörg
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project packaged-jmock has an issue affecting its community integration.
This issue
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project packaged-jmock has an issue affecting its community integration.
This issue
