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

[Nat P. <nat...@b1...>]

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
> 
> 
> -------------------------------------------------------
> 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