Java Mailing List Archive

http://www.gg3721.com/

Home » user.jmock »

[jmock-user] Asserts are suddenly ambiguous

Larry Edelstein

2008-07-07

Replies: Find Java Web Hosting

Author LoginPost Reply
Hi all -

I've been using JMock for years.  Suddenly I'm having trouble. 

I'm on 2.4, and have just realized that I should be using the JUnit-4-specific classes in JMock (the JUnit4Mockery, and the JMock test runner).

I am running inside of Eclipse.

Previously I was using the JUnit jar that Eclipse furnishes you with for your classpath - 4_4.3.1.  When I added the RunWith annotation to my test case, Eclipse began to complain that the JUnit4ClassRunner class was unreachable.  So I removed this item from the classpath and added the real JUnit 4.4 jar. That msg went away, but now I have this for many of my assertions:

"The method assertEquals(Object, Object) is ambiguous for the type ..."

I don't get it on every assert, but many of them.

Before I hit the sack, I'm posting this, maybe someone has a clue?

Larry Edelstein
Principal Software Engineer
LiveVox
ribs@acm.org





©2008 gg3721.com - Jax Systems, LLC, U.S.A.