You can subscribe to this list here.
2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(13) |
Aug
(151) |
Sep
(21) |
Oct
(6) |
Nov
(70) |
Dec
(8) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2002 |
Jan
(47) |
Feb
(66) |
Mar
(23) |
Apr
(115) |
May
(24) |
Jun
(53) |
Jul
(10) |
Aug
(279) |
Sep
(84) |
Oct
(149) |
Nov
(138) |
Dec
(52) |
2003 |
Jan
(22) |
Feb
(20) |
Mar
(29) |
Apr
(106) |
May
(170) |
Jun
(122) |
Jul
(70) |
Aug
(64) |
Sep
(27) |
Oct
(71) |
Nov
(49) |
Dec
(9) |
2004 |
Jan
(7) |
Feb
(38) |
Mar
(3) |
Apr
(9) |
May
(22) |
Jun
(4) |
Jul
(1) |
Aug
(2) |
Sep
(2) |
Oct
|
Nov
(15) |
Dec
(2) |
2005 |
Jan
(1) |
Feb
(1) |
Mar
|
Apr
(1) |
May
(28) |
Jun
(3) |
Jul
(11) |
Aug
(5) |
Sep
(1) |
Oct
(5) |
Nov
(2) |
Dec
(3) |
2006 |
Jan
(8) |
Feb
(3) |
Mar
(8) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Nat P. <nat...@b1...> - 2004-02-04 15:49:08
|
Oops, I forgot to add my intended point to the last email. That is, perhaps gump output should be sent to a different list, mockobjects-gump for example. What do people think? Cheers, Nat. |
From: Nat P. <nat...@b1...> - 2004-02-04 15:47:54
|
On Wed, 2004-02-04 at 13:05, Stefan Bodewig wrote: > The email based nagging system has been Gump's traditional approach > and it has done an outstanding job in many cases. I agree that it is > plain annoying if it comes unwanted. > > Maybe we can improve the nagging part in the Python implementation to > be configurable on a project level. Some projects may want a nightly > report even on successful builds as confirmation, others may only want > to get notified on status changes (as you describe it). I think the issue in this case is that some of the team added the project to gump and others did not know about it. So really, it's an internal communication and process issue that has brought to light the need to agree on how we use the HEAD branch. Which is a good thing. Another issue is how does Gump handle acceptance tests? A convention we are using on jmock is to allow failing acceptance tests into CVS to show what needs to be done long-term. The library itself and the unit tests will always compile and the unit tests will always pass, but the acceptance tests can fail or even not compile at all. Cheers, Nat. |
From: Stefan B. <bo...@ap...> - 2004-02-04 13:06:03
|
On Wed, 4 Feb 2004, Nat Pryce <nat...@b1...> wrote: > Considering what Gump is meant to be used for, would it be better > for it to be "edge triggered" rather than "level triggered". It depends on the community you want to reach. Sometimes it takes repeated nagging to get the message through. Sometimes you generate the opposite effect by nagging, i.e. mails get ignored. > That is, should it send a message when a project fails to build, and > then sends a message when the project builds successfully again, > instead of sending a message every time it fails to build a broken > project? Yes, this would certainly be an option, and I think much of the statistics sthe new Python implementation of Gump collects can be used for that. We also generate RSS feeds that contain exactly these types of status changes IIRC. The email based nagging system has been Gump's traditional approach and it has done an outstanding job in many cases. I agree that it is plain annoying if it comes unwanted. Maybe we can improve the nagging part in the Python implementation to be configurable on a project level. Some projects may want a nightly report even on successful builds as confirmation, others may only want to get notified on status changes (as you describe it). Stefan |
From: Nat P. <nat...@b1...> - 2004-02-04 09:53:15
|
Considering what Gump is meant to be used for, would it be better for it to be "edge triggered" rather than "level triggered". That is, should it send a message when a project fails to build, and then sends a message when the project builds successfully again, instead of sending a message every time it fails to build a broken project? Cheers, Nat. _______________________ Dr. Nathaniel Pryce B13media Ltd. http://www.b13media.com +44 (0)7712 526 661 ----- Original Message ----- From: "Stefan Bodewig" <bo...@ap...> To: <gu...@ja...> Cc: <moc...@li...> Sent: Wednesday, February 04, 2004 9:04 AM Subject: Re: [MO-java-dev] compilation problem for mockobjects > On Tue, 3 Feb 2004, Vincent Massol <vm...@pi...> wrote: > > > I haven't been following the discussion but for the record I think > > using Gump is great and should be continued. > > I've seen a similar comment by Jeff in the archives (I tried to > subscribe to mockobjects-java-dev but SF's mailing list manager was > down yesterday, so I'm not yet subscribed). > > What I've done so far is that I've added mockobjects-0.09 and made all > projects in Gump depend on that. Gump still tries to build the CVS > HEAD revisions of mockobjects[1][2], but no other project depends on > it and I've turned of nagging. > > Cheers > > Stefan > > Footnotes: > [1] http://gump.covalent.net/log/mockobjects-cvs-head.html > > [2] it currently doesn't work in the new Python version, but we'll > work on it. > > > > ------------------------------------------------------- > 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: Stefan B. <bo...@ap...> - 2004-02-04 09:04:16
|
On Tue, 3 Feb 2004, Vincent Massol <vm...@pi...> wrote: > I haven't been following the discussion but for the record I think > using Gump is great and should be continued. I've seen a similar comment by Jeff in the archives (I tried to subscribe to mockobjects-java-dev but SF's mailing list manager was down yesterday, so I'm not yet subscribed). What I've done so far is that I've added mockobjects-0.09 and made all projects in Gump depend on that. Gump still tries to build the CVS HEAD revisions of mockobjects[1][2], but no other project depends on it and I've turned of nagging. Cheers Stefan Footnotes: [1] http://gump.covalent.net/log/mockobjects-cvs-head.html [2] it currently doesn't work in the new Python version, but we'll work on it. |
From: Vincent M. <vm...@pi...> - 2004-02-03 22:17:34
|
I haven't been following the discussion but for the record I think using Gump is great and should be continued. That said, I'm no longer active on the mockobjects project so I'll let active members decide on this. Thanks -Vincent PS: Stefan, I do really appreciate Gump and as soon as I find a few minutes I'll continue working towards helping make the cactus build work with Gumpy. > -----Original Message----- > From: Stefan Bodewig [mailto:bo...@ap...] > Sent: 03 February 2004 08:20 > To: gu...@ja... > Cc: mockobjects-java-dev > Subject: Re: [MO-java-dev] compilation problem for mockobjects > > On Mon, 02 Feb 2004, Nat Pryce <nat...@b1...> > wrote: > > > Who put mockobjects.com into gump? Whoever it is, they should sort > > out the problem. > > Oh my. > > Having mockobjects built by Gump used to be appreciated by Jeff and > Vincent. Given that cactus relies on mockobjects and also relies on > Gump quite a bit, this seemed natural. > > There is no problem with removing mockobjects from Gump if that is > what you want. I'll take care of it. > > Cheers > > Stefan > > --------------------------------------------------------------------- > To unsubscribe, e-mail: gum...@ja... > For additional commands, e-mail: gum...@ja... |
From: Jeff M. <je...@cu...> - 2004-02-03 10:56:17
|
No please keep it in gump, we obviously need it there or we wouldn't be running around trying to fix things ;) I really don't see that five mails over five days is really a huge price to pay (Currently I'm getting 4000 a day courtesy of MyDoom) I've now removed a couple of dodge files Nat pointed me to so hopefully that's us sorted for a bit. On Tue, 2004-02-03 at 07:20, Stefan Bodewig wrote: > On Mon, 02 Feb 2004, Nat Pryce <nat...@b1...> > wrote: > > > Who put mockobjects.com into gump? Whoever it is, they should sort > > out the problem. > > Oh my. > > Having mockobjects built by Gump used to be appreciated by Jeff and > Vincent. Given that cactus relies on mockobjects and also relies on > Gump quite a bit, this seemed natural. > > There is no problem with removing mockobjects from Gump if that is > what you want. I'll take care of it. > > Cheers > > Stefan > > > ------------------------------------------------------- > 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 -- Jeff Martin Memetic Engineer http://www.custommonkey.org/ |
From: Jeff M. <cus...@us...> - 2004-02-03 10:53:47
|
Update of /cvsroot/mockobjects/mockobjects-java/src/core/com/mockobjects/dynamic In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv13666/src/core/com/mockobjects/dynamic Removed Files: CallOnceStub.java MethodExpectation.java Log Message: Remove old files which break the build --- CallOnceStub.java DELETED --- --- MethodExpectation.java DELETED --- |
From: Jeff M. <cus...@us...> - 2004-02-03 10:53:47
|
Update of /cvsroot/mockobjects/mockobjects-java/src/core/test/mockobjects/dynamic In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv13666/src/core/test/mockobjects/dynamic Removed Files: InvocationMatcherTest.java MethodExpectationTest.java Log Message: Remove old files which break the build --- InvocationMatcherTest.java DELETED --- --- MethodExpectationTest.java DELETED --- |
From: Stefan B. <bo...@ap...> - 2004-02-03 07:20:30
|
On Mon, 02 Feb 2004, Nat Pryce <nat...@b1...> wrote: > Who put mockobjects.com into gump? Whoever it is, they should sort > out the problem. Oh my. Having mockobjects built by Gump used to be appreciated by Jeff and Vincent. Given that cactus relies on mockobjects and also relies on Gump quite a bit, this seemed natural. There is no problem with removing mockobjects from Gump if that is what you want. I'll take care of it. Cheers Stefan |
From: Jeff Martin<je...@cu...> - 2004-02-03 06:28:31
|
Project: mockobjects State: Failed URL: http://lsd.student.utwente.nl/gump/mockobjects/mockobjects.html ------------------------------------------------- G U M P Y Annotations: - Info - Made directory [/data/gump/mockobjects/out/core/classes] - Info - Made directory [/data/gump/mockobjects/out/jdk/classes] - Error - Failed with reason build failed ------------------------------------------------- G U M P Y Work Name: build_mockobjects_mockobjects (Type: Build) State: Failed Elapsed: 0 hours, 0 minutes, 7 seconds Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/data/gump/xml-xerces2/java/build/xercesImpl.jar:/data/gump/xml-xerces2/java/build/xmlParserAPIs.jar org.apache.tools.ant.Main -Dbuild.clonevm=true -Dgump.merge=/data/gump/gump/work/merge.xml -Dbuild.sysclasspath=only -Dproject.version=20040203 [Working Directory: /data/gump/mockobjects] --------------------------------------------- [javac] symbol : class Arguments [javac] location: interface com.mockobjects.dynamic.InvocationMatcher [javac] InvocationMatcher.Arguments matcher = new InvocationMatcher.Arguments(new Constraint[0]); [javac] ^ [javac] /data/gump/mockobjects/src/core/test/mockobjects/dynamic/InvocationMatcherTest.java:51: cannot resolve symbol [javac] symbol : class Arguments [javac] location: interface com.mockobjects.dynamic.InvocationMatcher [javac] InvocationMatcher.Arguments matcher = new InvocationMatcher.Arguments(new Constraint[0]); [javac] ^ [javac] /data/gump/mockobjects/src/core/test/mockobjects/dynamic/InvocationMatcherTest.java:51: cannot resolve symbol [javac] symbol : class Arguments [javac] location: interface com.mockobjects.dynamic.InvocationMatcher [javac] InvocationMatcher.Arguments matcher = new InvocationMatcher.Arguments(new Constraint[0]); [javac] ^ [javac] /data/gump/mockobjects/src/core/test/mockobjects/dynamic/InvocationMatcherTest.java:57: cannot resolve symbol [javac] symbol : class Arguments [javac] location: interface com.mockobjects.dynamic.InvocationMatcher [javac] InvocationMatcher.Arguments matcher = [javac] ^ [javac] /data/gump/mockobjects/src/core/test/mockobjects/dynamic/InvocationMatcherTest.java:58: cannot resolve symbol [javac] symbol : class Arguments [javac] location: interface com.mockobjects.dynamic.InvocationMatcher [javac] new InvocationMatcher.Arguments( [javac] ^ [javac] /data/gump/mockobjects/src/core/test/mockobjects/dynamic/InvocationMatcherTest.java:65: cannot resolve symbol [javac] symbol : class Arguments [javac] location: interface com.mockobjects.dynamic.InvocationMatcher [javac] InvocationMatcher.Arguments matcher = [javac] ^ [javac] /data/gump/mockobjects/src/core/test/mockobjects/dynamic/InvocationMatcherTest.java:66: cannot resolve symbol [javac] symbol : class Arguments [javac] location: interface com.mockobjects.dynamic.InvocationMatcher [javac] new InvocationMatcher.Arguments( [javac] ^ [javac] /data/gump/mockobjects/src/core/test/mockobjects/dynamic/InvocationMatcherTest.java:73: cannot resolve symbol [javac] symbol : class Arguments [javac] location: interface com.mockobjects.dynamic.InvocationMatcher [javac] InvocationMatcher.Arguments matcher = [javac] ^ [javac] /data/gump/mockobjects/src/core/test/mockobjects/dynamic/InvocationMatcherTest.java:74: cannot resolve symbol [javac] symbol : class Arguments [javac] location: interface com.mockobjects.dynamic.InvocationMatcher [javac] new InvocationMatcher.Arguments( [javac] ^ [javac] 23 errors BUILD FAILED /data/gump/mockobjects/build.xml:121: Compile failed; see the compiler error output for details. Total time: 6 seconds --------------------------------------------- ------------------------------------------------- G U M P Y RSS: http://lsd.student.utwente.nl/gump/mockobjects/mockobjects.rss | Atom: http://lsd.student.utwente.nl/gump/mockobjects/mockobjects.atom -- Gump http://jakarta.apache.org/gump [lsd] |
From: shivaken <shi...@e-...> - 2004-02-03 00:51:08
|
Thanks for implementing MockHttpSession.getId. I need MockHttpServletResponse.encodeURL and encodeRedirectURL . Then I wrote a patch constructed with encodeURL, encodeRedirectURL and setupEncodeURL. But as you can see at MockHttpSession patch, I don't know proper way to write mockobject. I want you to implement then too. Now I am writing a class that extends java.io.BufferedReader for my job. But I cannot find any good mock implementations at com.mockobjects.io . It seems that I cannot use dynamic mockobject, because It is not interface. So I am going to write MockBufferedReader. Thanks again. -- -- shivaken antshell: Ant command line front end http://www.antshell.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. |
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: 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: <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 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: 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: <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: Jeff Martin<je...@cu...> - 2004-02-02 06:18:03
|
Project: mockobjects State: Failed URL: http://lsd.student.utwente.nl/gump/mockobjects/mockobjects.html ------------------------------------------------- G U M P Y Annotations: - Info - Made directory [/data/gump/mockobjects/out/core/classes] - Info - Made directory [/data/gump/mockobjects/out/jdk/classes] - Error - Failed with reason build failed ------------------------------------------------- G U M P Y Work Name: build_mockobjects_mockobjects (Type: Build) State: Failed Elapsed: 0 hours, 0 minutes, 8 seconds Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/data/gump/xml-xerces2/java/build/xercesImpl.jar:/data/gump/xml-xerces2/java/build/xmlParserAPIs.jar org.apache.tools.ant.Main -Dbuild.clonevm=true -Dgump.merge=/data/gump/gump/work/merge.xml -Dbuild.sysclasspath=only -Dproject.version=20040202 [Working Directory: /data/gump/mockobjects] --------------------------------------------- [javac] symbol : class Arguments [javac] location: interface com.mockobjects.dynamic.InvocationMatcher [javac] InvocationMatcher.Arguments matcher = new InvocationMatcher.Arguments(new Constraint[0]); [javac] ^ [javac] /data/gump/mockobjects/src/core/test/mockobjects/dynamic/InvocationMatcherTest.java:51: cannot resolve symbol [javac] symbol : class Arguments [javac] location: interface com.mockobjects.dynamic.InvocationMatcher [javac] InvocationMatcher.Arguments matcher = new InvocationMatcher.Arguments(new Constraint[0]); [javac] ^ [javac] /data/gump/mockobjects/src/core/test/mockobjects/dynamic/InvocationMatcherTest.java:51: cannot resolve symbol [javac] symbol : class Arguments [javac] location: interface com.mockobjects.dynamic.InvocationMatcher [javac] InvocationMatcher.Arguments matcher = new InvocationMatcher.Arguments(new Constraint[0]); [javac] ^ [javac] /data/gump/mockobjects/src/core/test/mockobjects/dynamic/InvocationMatcherTest.java:57: cannot resolve symbol [javac] symbol : class Arguments [javac] location: interface com.mockobjects.dynamic.InvocationMatcher [javac] InvocationMatcher.Arguments matcher = [javac] ^ [javac] /data/gump/mockobjects/src/core/test/mockobjects/dynamic/InvocationMatcherTest.java:58: cannot resolve symbol [javac] symbol : class Arguments [javac] location: interface com.mockobjects.dynamic.InvocationMatcher [javac] new InvocationMatcher.Arguments( [javac] ^ [javac] /data/gump/mockobjects/src/core/test/mockobjects/dynamic/InvocationMatcherTest.java:65: cannot resolve symbol [javac] symbol : class Arguments [javac] location: interface com.mockobjects.dynamic.InvocationMatcher [javac] InvocationMatcher.Arguments matcher = [javac] ^ [javac] /data/gump/mockobjects/src/core/test/mockobjects/dynamic/InvocationMatcherTest.java:66: cannot resolve symbol [javac] symbol : class Arguments [javac] location: interface com.mockobjects.dynamic.InvocationMatcher [javac] new InvocationMatcher.Arguments( [javac] ^ [javac] /data/gump/mockobjects/src/core/test/mockobjects/dynamic/InvocationMatcherTest.java:73: cannot resolve symbol [javac] symbol : class Arguments [javac] location: interface com.mockobjects.dynamic.InvocationMatcher [javac] InvocationMatcher.Arguments matcher = [javac] ^ [javac] /data/gump/mockobjects/src/core/test/mockobjects/dynamic/InvocationMatcherTest.java:74: cannot resolve symbol [javac] symbol : class Arguments [javac] location: interface com.mockobjects.dynamic.InvocationMatcher [javac] new InvocationMatcher.Arguments( [javac] ^ [javac] 23 errors BUILD FAILED /data/gump/mockobjects/build.xml:121: Compile failed; see the compiler error output for details. Total time: 7 seconds --------------------------------------------- ------------------------------------------------- G U M P Y RSS: http://lsd.student.utwente.nl/gump/mockobjects/mockobjects.rss | Atom: http://lsd.student.utwente.nl/gump/mockobjects/mockobjects.atom -- Gump http://jakarta.apache.org/gump [lsd] |
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: Jeff Martin<je...@cu...> - 2004-02-01 06:36:36
|
Project: mockobjects State: Failed URL: http://lsd.student.utwente.nl/gump/mockobjects/mockobjects.html ------------------------------------------------- G U M P Y Annotations: - Info - Made directory [/data/gump/mockobjects/out/core/classes] - Info - Made directory [/data/gump/mockobjects/out/jdk/classes] - Error - Failed with reason build failed ------------------------------------------------- G U M P Y Work Name: build_mockobjects_mockobjects (Type: Build) State: Failed Elapsed: 0 hours, 0 minutes, 8 seconds Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/data/gump/xml-xerces2/java/build/xercesImpl.jar:/data/gump/xml-xerces2/java/build/xmlParserAPIs.jar org.apache.tools.ant.Main -Dbuild.clonevm=true -Dgump.merge=/data/gump/gump/work/merge.xml -Dbuild.sysclasspath=only -Dproject.version=20040201 [Working Directory: /data/gump/mockobjects] --------------------------------------------- [javac] symbol : class Arguments [javac] location: interface com.mockobjects.dynamic.InvocationMatcher [javac] InvocationMatcher.Arguments matcher = new InvocationMatcher.Arguments(new Constraint[0]); [javac] ^ [javac] /data/gump/mockobjects/src/core/test/mockobjects/dynamic/InvocationMatcherTest.java:51: cannot resolve symbol [javac] symbol : class Arguments [javac] location: interface com.mockobjects.dynamic.InvocationMatcher [javac] InvocationMatcher.Arguments matcher = new InvocationMatcher.Arguments(new Constraint[0]); [javac] ^ [javac] /data/gump/mockobjects/src/core/test/mockobjects/dynamic/InvocationMatcherTest.java:51: cannot resolve symbol [javac] symbol : class Arguments [javac] location: interface com.mockobjects.dynamic.InvocationMatcher [javac] InvocationMatcher.Arguments matcher = new InvocationMatcher.Arguments(new Constraint[0]); [javac] ^ [javac] /data/gump/mockobjects/src/core/test/mockobjects/dynamic/InvocationMatcherTest.java:57: cannot resolve symbol [javac] symbol : class Arguments [javac] location: interface com.mockobjects.dynamic.InvocationMatcher [javac] InvocationMatcher.Arguments matcher = [javac] ^ [javac] /data/gump/mockobjects/src/core/test/mockobjects/dynamic/InvocationMatcherTest.java:58: cannot resolve symbol [javac] symbol : class Arguments [javac] location: interface com.mockobjects.dynamic.InvocationMatcher [javac] new InvocationMatcher.Arguments( [javac] ^ [javac] /data/gump/mockobjects/src/core/test/mockobjects/dynamic/InvocationMatcherTest.java:65: cannot resolve symbol [javac] symbol : class Arguments [javac] location: interface com.mockobjects.dynamic.InvocationMatcher [javac] InvocationMatcher.Arguments matcher = [javac] ^ [javac] /data/gump/mockobjects/src/core/test/mockobjects/dynamic/InvocationMatcherTest.java:66: cannot resolve symbol [javac] symbol : class Arguments [javac] location: interface com.mockobjects.dynamic.InvocationMatcher [javac] new InvocationMatcher.Arguments( [javac] ^ [javac] /data/gump/mockobjects/src/core/test/mockobjects/dynamic/InvocationMatcherTest.java:73: cannot resolve symbol [javac] symbol : class Arguments [javac] location: interface com.mockobjects.dynamic.InvocationMatcher [javac] InvocationMatcher.Arguments matcher = [javac] ^ [javac] /data/gump/mockobjects/src/core/test/mockobjects/dynamic/InvocationMatcherTest.java:74: cannot resolve symbol [javac] symbol : class Arguments [javac] location: interface com.mockobjects.dynamic.InvocationMatcher [javac] new InvocationMatcher.Arguments( [javac] ^ [javac] 23 errors BUILD FAILED /data/gump/mockobjects/build.xml:121: Compile failed; see the compiler error output for details. Total time: 6 seconds --------------------------------------------- ------------------------------------------------- G U M P Y RSS: http://lsd.student.utwente.nl/gump/mockobjects/mockobjects.rss | Atom: http://lsd.student.utwente.nl/gump/mockobjects/mockobjects.atom -- Gump http://jakarta.apache.org/gump [lsd] |
From: Jeff Martin<je...@cu...> - 2004-02-01 02:43:37
|
Project: mockobjects State: Failed URL: http://lsd.student.utwente.nl/gump/mockobjects/mockobjects.html RSS: http://lsd.student.utwente.nl/gump/mockobjects/mockobjects.rss Atom: http://lsd.student.utwente.nl/gump/mockobjects/mockobjects.atom ------------------------------------------------- G U M P Y Annotations: - Info - Made directory [/data/gump/mockobjects/out/core/classes] - Info - Made directory [/data/gump/mockobjects/out/jdk/classes] - Error - Failed with reason build failed ------------------------------------------------- G U M P Y Work Name: build_mockobjects_mockobjects (Type: Build) State: Failed Elapsed: 0 hours, 0 minutes, 7 seconds Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/data/gump/xml-xerces2/java/build/xercesImpl.jar:/data/gump/xml-xerces2/java/build/xmlParserAPIs.jar org.apache.tools.ant.Main -Dbuild.clonevm=true -Dgump.merge=/data/gump/gump/work/merge.xml -Dbuild.sysclasspath=only -Dproject.version=20040130 [Working Directory: /data/gump/mockobjects] --------------------------------------------- [javac] symbol : class Arguments [javac] location: interface com.mockobjects.dynamic.InvocationMatcher [javac] InvocationMatcher.Arguments matcher = new InvocationMatcher.Arguments(new Constraint[0]); [javac] ^ [javac] /data/gump/mockobjects/src/core/test/mockobjects/dynamic/InvocationMatcherTest.java:51: cannot resolve symbol [javac] symbol : class Arguments [javac] location: interface com.mockobjects.dynamic.InvocationMatcher [javac] InvocationMatcher.Arguments matcher = new InvocationMatcher.Arguments(new Constraint[0]); [javac] ^ [javac] /data/gump/mockobjects/src/core/test/mockobjects/dynamic/InvocationMatcherTest.java:51: cannot resolve symbol [javac] symbol : class Arguments [javac] location: interface com.mockobjects.dynamic.InvocationMatcher [javac] InvocationMatcher.Arguments matcher = new InvocationMatcher.Arguments(new Constraint[0]); [javac] ^ [javac] /data/gump/mockobjects/src/core/test/mockobjects/dynamic/InvocationMatcherTest.java:57: cannot resolve symbol [javac] symbol : class Arguments [javac] location: interface com.mockobjects.dynamic.InvocationMatcher [javac] InvocationMatcher.Arguments matcher = [javac] ^ [javac] /data/gump/mockobjects/src/core/test/mockobjects/dynamic/InvocationMatcherTest.java:58: cannot resolve symbol [javac] symbol : class Arguments [javac] location: interface com.mockobjects.dynamic.InvocationMatcher [javac] new InvocationMatcher.Arguments( [javac] ^ [javac] /data/gump/mockobjects/src/core/test/mockobjects/dynamic/InvocationMatcherTest.java:65: cannot resolve symbol [javac] symbol : class Arguments [javac] location: interface com.mockobjects.dynamic.InvocationMatcher [javac] InvocationMatcher.Arguments matcher = [javac] ^ [javac] /data/gump/mockobjects/src/core/test/mockobjects/dynamic/InvocationMatcherTest.java:66: cannot resolve symbol [javac] symbol : class Arguments [javac] location: interface com.mockobjects.dynamic.InvocationMatcher [javac] new InvocationMatcher.Arguments( [javac] ^ [javac] /data/gump/mockobjects/src/core/test/mockobjects/dynamic/InvocationMatcherTest.java:73: cannot resolve symbol [javac] symbol : class Arguments [javac] location: interface com.mockobjects.dynamic.InvocationMatcher [javac] InvocationMatcher.Arguments matcher = [javac] ^ [javac] /data/gump/mockobjects/src/core/test/mockobjects/dynamic/InvocationMatcherTest.java:74: cannot resolve symbol [javac] symbol : class Arguments [javac] location: interface com.mockobjects.dynamic.InvocationMatcher [javac] new InvocationMatcher.Arguments( [javac] ^ [javac] 23 errors BUILD FAILED /data/gump/mockobjects/build.xml:121: Compile failed; see the compiler error output for details. Total time: 6 seconds --------------------------------------------- -- Gump http://jakarta.apache.org/gump [lsd] |
From: Jeff Martin<je...@cu...> - 2004-01-31 07:28:30
|
Project: mockobjects State: Failed URL: http://lsd.student.utwente.nl/gump/mockobjects/mockobjects.html ------------------------------------------------- G U M P Y Annotations: - Info - Made directory [/data/gump/mockobjects/out/core/classes] - Info - Made directory [/data/gump/mockobjects/out/jdk/classes] - Error - Failed with reason build failed ------------------------------------------------- G U M P Y Work Name: build_mockobjects_mockobjects (Type: Build) State: Failed Elapsed: 0 hours, 0 minutes, 10 seconds Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/data/gump/xml-xerces2/java/build/xercesImpl.jar:/data/gump/xml-xerces2/java/build/xmlParserAPIs.jar org.apache.tools.ant.Main -Dbuild.clonevm=true -Dgump.merge=/data/gump/gump/work/merge.xml -Dbuild.sysclasspath=only -Dproject.version=20040131 [Working Directory: /data/gump/mockobjects] --------------------------------------------- [javac] symbol : class Arguments [javac] location: interface com.mockobjects.dynamic.InvocationMatcher [javac] InvocationMatcher.Arguments matcher = new InvocationMatcher.Arguments(new Constraint[0]); [javac] ^ [javac] /data/gump/mockobjects/src/core/test/mockobjects/dynamic/InvocationMatcherTest.java:51: cannot resolve symbol [javac] symbol : class Arguments [javac] location: interface com.mockobjects.dynamic.InvocationMatcher [javac] InvocationMatcher.Arguments matcher = new InvocationMatcher.Arguments(new Constraint[0]); [javac] ^ [javac] /data/gump/mockobjects/src/core/test/mockobjects/dynamic/InvocationMatcherTest.java:51: cannot resolve symbol [javac] symbol : class Arguments [javac] location: interface com.mockobjects.dynamic.InvocationMatcher [javac] InvocationMatcher.Arguments matcher = new InvocationMatcher.Arguments(new Constraint[0]); [javac] ^ [javac] /data/gump/mockobjects/src/core/test/mockobjects/dynamic/InvocationMatcherTest.java:57: cannot resolve symbol [javac] symbol : class Arguments [javac] location: interface com.mockobjects.dynamic.InvocationMatcher [javac] InvocationMatcher.Arguments matcher = [javac] ^ [javac] /data/gump/mockobjects/src/core/test/mockobjects/dynamic/InvocationMatcherTest.java:58: cannot resolve symbol [javac] symbol : class Arguments [javac] location: interface com.mockobjects.dynamic.InvocationMatcher [javac] new InvocationMatcher.Arguments( [javac] ^ [javac] /data/gump/mockobjects/src/core/test/mockobjects/dynamic/InvocationMatcherTest.java:65: cannot resolve symbol [javac] symbol : class Arguments [javac] location: interface com.mockobjects.dynamic.InvocationMatcher [javac] InvocationMatcher.Arguments matcher = [javac] ^ [javac] /data/gump/mockobjects/src/core/test/mockobjects/dynamic/InvocationMatcherTest.java:66: cannot resolve symbol [javac] symbol : class Arguments [javac] location: interface com.mockobjects.dynamic.InvocationMatcher [javac] new InvocationMatcher.Arguments( [javac] ^ [javac] /data/gump/mockobjects/src/core/test/mockobjects/dynamic/InvocationMatcherTest.java:73: cannot resolve symbol [javac] symbol : class Arguments [javac] location: interface com.mockobjects.dynamic.InvocationMatcher [javac] InvocationMatcher.Arguments matcher = [javac] ^ [javac] /data/gump/mockobjects/src/core/test/mockobjects/dynamic/InvocationMatcherTest.java:74: cannot resolve symbol [javac] symbol : class Arguments [javac] location: interface com.mockobjects.dynamic.InvocationMatcher [javac] new InvocationMatcher.Arguments( [javac] ^ [javac] 23 errors BUILD FAILED /data/gump/mockobjects/build.xml:121: Compile failed; see the compiler error output for details. Total time: 9 seconds --------------------------------------------- ------------------------------------------------- G U M P Y RSS: http://lsd.student.utwente.nl/gump/mockobjects/mockobjects.rss | Atom: http://lsd.student.utwente.nl/gump/mockobjects/mockobjects.atom -- Gump http://jakarta.apache.org/gump [lsd] |