Menu
▾
▴
mockobjects-java-dev
|
From: <an...@an...> - 2004-02-01 21:41:21
|
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 |
|
From: <an...@an...> - 2004-02-02 13:45:55
|
Steve Freeman wrote: > 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: > >> 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 >> > 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/co= re/com/mockobjects/dynamic/InvocationMatcher.java?r1=3D1.3&r2=3D1.4 Antoine |
|
From: Nat P. <nat...@b1...> - 2004-02-02 13:54:54
|
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 |
|
From: Jeff M. <je...@cu...> - 2004-02-02 14:02:53
|
Generally gump is configured to run against HEAD as it is designed to highlight incompatibilities between future releases of projects. The problem isn't gump it's the code in CVS. It's really bad to checkin code which doesn't compile no matter where it is. Gump is correctly highlighting a problem that we need to resolve. On Mon, 2004-02-02 at 13:54, 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. >=20 > Cheers, > Nat. >=20 > On Mon, 2004-02-02 at 13:43, Antoine L=C3=A9vy-Lambert wrote: > > 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=C3=A9vy-Lambert wrote: > > > > > >> Hi Steve, > > >> > > >> do you think you will be able to fix mockobjects so that it compil= es > > >> 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 > > >> > > > > > For me the failure does not seem related to Gump : > >=20 > > core.test.mockobjects.dynamic.InvocationMatcherTest > >=20 > > 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/sr= c/core/com/mockobjects/dynamic/InvocationMatcher.java?r1=3D1.3&r2=3D1.4 > >=20 > > Antoine > >=20 > >=20 > > ------------------------------------------------------- > > 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 >=20 >=20 >=20 > ------------------------------------------------------- > 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 --=20 Jeff Martin =20 Memetic Engineer =20 http://www.custommonkey.org/ |
|
From: <an...@an...> - 2004-02-02 15:37:09
|
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 |
|
From: Nat P. <nat...@b1...> - 2004-02-02 15:33:24
|
Who put mockobjects.com into gump? Whoever it is, they should sort out the problem. Cheers, Nat. On Mon, 2004-02-02 at 15:18, Antoine Lévy-Lambert wrote: > 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 |
|
From: Jeff M. <je...@cu...> - 2004-02-02 16:21:33
|
Err, it's probably coming from the original Apache Gump hence my name on the mail. But it's not they're problem it's ours. It's the responsibility of whoever checked in the broken code into CVS. People running Gump are doing us a favour by checking our code, as a responsible project we should be ensure that our code compiles and that all the tests are passing. On Mon, 2004-02-02 at 15:33, Nat Pryce wrote: > Who put mockobjects.com into gump? Whoever it is, they should sort out > the problem. > > Cheers, > Nat. > -- Jeff Martin Memetic Engineer http://www.custommonkey.org/ |
|
From: Jeff M. <je...@cu...> - 2004-02-02 16:50:06
|
On Mon, 2004-02-02 at 16:25, Jeff Martin wrote: > Err, it's probably coming from the original Apache Gump hence my name on > the mail. > > Just to clarify, the configuration came from Apache not the mail. -- Jeff Martin Memetic Engineer http://www.custommonkey.org/ |
|
From: Nat P. <nat...@b1...> - 2004-02-02 16:52:01
|
On Mon, 2004-02-02 at 16:25, Jeff Martin wrote: > Err, it's probably coming from the original Apache Gump hence my name on > the mail. > > But it's not they're problem it's ours. It's the responsibility of > whoever checked in the broken code into CVS. I don't disagree with that. > People running Gump are > doing us a favour by checking our code, as a responsible project we > should be ensure that our code compiles and that all the tests are > passing. That's as maybe. It would be nice if they had let us know what they were doing before they started sending loads of error messages onto the dev mailing list. Cheers, Nat. |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X