You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@gump.apache.org by Antoine Lévy-Lambert <an...@antbuild.com> on 2004/02/01 22:39:22 UTC
compilation problem for mockobjects
Hi,
mockobjects does not compile in gump [1], and a lot of projects are
dependent upon mockobjects [2].:
Would you be so kind to fix it ?
I have entered a bug report in your bug tracking system too. [3]
Thanks in advance, :-)
Antoine Levy-Lambert
[1] http://lsd.student.utwente.nl/gump/mockobjects/mockobjects.html
[2]
http://lsd.student.utwente.nl/gump/mockobjects/mockobjects_details.html#Full+Project+Dependees
[3]
http://sourceforge.net/tracker/index.php?func=detail&aid=888728&group_id=18189&atid=118189
Re: [MO-java-dev] compilation problem for mockobjects
Posted by Antoine Lévy-Lambert <an...@antbuild.com>.
Steve Freeman wrote:
> Is this a new installation of gump you've set up? Or one that was
> running before?
>
What I know is that gump is migrating to a new implementation written in
Python called gumpy.
The look and feel of the new implementation is also nicer than before.
Now concerning the metadata and the way projects are set up, I do not
think there is anything revolutionary yet.
Antoine
> S.
>
> Antoine Lévy-Lambert wrote:
>
>> Hi,
>>
>> mockobjects does not compile in gump [1], and a lot of projects are
>> dependent upon mockobjects [2].:
>>
>> Would you be so kind to fix it ?
>>
>> I have entered a bug report in your bug tracking system too. [3]
>>
>> Thanks in advance, :-)
>>
>> Antoine Levy-Lambert
>>
>> [1] http://lsd.student.utwente.nl/gump/mockobjects/mockobjects.html
>> [2]
>> http://lsd.student.utwente.nl/gump/mockobjects/mockobjects_details.html#Full+Project+Dependees
>>
>> [3]
>> http://sourceforge.net/tracker/index.php?func=detail&aid=888728&group_id=18189&atid=118189
>>
>>
>>
>>
>>
>>
>
Re: [MO-java-dev] compilation problem for mockobjects
Posted by Antoine Lévy-Lambert <an...@antbuild.com>.
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évy-Lambert wrote:
>
>
>>Steve Freeman wrote:
>>
>>
>>
>>>We're investigating, since someone else did the gump configuration and
>>>I don't actually know what's involved. A bit tricky since I'm away on
>>>site at the moment.
>>>
>>>S.
>>>
>>>Antoine Lévy-Lambert wrote:
>>>
>>>
>>>
>>>>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
>>>>ant-xdocs-proposals.
>>>>
>>>>A lot of other projects are dependent upon mockobjects.
>>>>
>>>>Cheers,
>>>>
>>>>Antoine
>>>>
>>>>
>>>>
>>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=1.3&r2=1.4
>>
>>Antoine
>>
>>
>>
>>
>>
>
>
Hi,
gump's job is really to test head revisions., and to test that the head
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
long time, then we can make some projects in gump dependent upon a
packaged version of mockobjects.
Antoine