Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Cannot Reproduce
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: nanowar
-
Labels:None
-
Number of attachments :
Description
NanoWebServletTestCase fails due to the mock object's failure to verify().
They are set to expectAndReturn() with methods that are never called within the scope of the tests.
Activity
Resolved.
I was using Eclipse to build, and I was adding jars manually.
I built using Maven and it passed, so I used the Maven Eclipse plugin to build a .classpath file and show which jars were being used. I manually added those to my build path... and got the green light. I don't know which jar actually broke the test.
Show
Miguel Paraz
added a comment - Resolved.
I was using Eclipse to build, and I was adding jars manually.
I built using Maven and it passed, so I used the Maven Eclipse plugin to build a .classpath file and show which jars were being used. I manually added those to my build path... and got the green light. I don't know which jar actually broke the test.
Miguel Paraz
added a comment - Resolved.
I was using Eclipse to build, and I was adding jars manually.
I built using Maven and it passed, so I used the Maven Eclipse plugin to build a .classpath file and show which jars were being used. I manually added those to my build path... and got the green light. I don't know which jar actually broke the test. Aslak Hellesøy
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Assignee | Aslak Hellesoy [ rinkrank ] | |
| Resolution | Cannot Reproduce [ 5 ] | |
| Status | Open [ 1 ] | Closed [ 6 ] |
Neither I or DamageControl (http://builds.codehaus.org/log/picocontainer/) get any errors.
1) Got a stack trace?
2) What's the date of your jmock-SNAPSHOT.jar? (Mine is from 29/11-2003 - http://dist.codehaus.org/jmock/jars/)