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

[<an...@an...>]

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=E9vy-Lambert wrote:
> =20
>
>>Steve Freeman wrote:
>>
>>   =20
>>
>>>We're investigating, since someone else did the gump configuration and=
=20
>>>I don't actually know what's involved. A bit tricky since I'm away on=20
>>>site at the moment.
>>>
>>>S.
>>>
>>>Antoine L=E9vy-Lambert wrote:
>>>
>>>     =20
>>>
>>>>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=20
>>>>ant-xdocs-proposals.
>>>>
>>>>A lot of other projects are dependent upon mockobjects.
>>>>
>>>>Cheers,
>>>>
>>>>Antoine
>>>>
>>>>       =20
>>>>
>>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=3D1.3&r2=3D1.4
>>
>>Antoine
>>
>>
>>
>>   =20
>>
> =20
>
Hi,

gump's job is really to test head revisions., and to test that the head=20
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=20
long time, then we can make some projects in gump dependent upon a=20
packaged version of mockobjects.


Antoine