[Bug 791263] Review Request: mockito - A Java mocking framework

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=791263

--- Comment #13 from Roman Kennke <rkennke at redhat.com> 2012-02-21 17:10:18 EST ---
(In reply to comment #12)
> (In reply to comment #9)
> >   - JUnit4 because users of Mockito certainly must include that otherwise
> > Mockito doesn't make sense.
> 
> I would not agree with that. Mockito can be easily used with TestNG as well as
> probably with any other testing framework/library for Java.
> JUnit is only internally used to run Mockito's own tests during a build
> process.

This is not exactly true. While I don't agree with the above logic as well (I
would include junit4 as runtime dependency), it is true that Mockito provides a
bunch of classes that subclass org.junit.runner.Runner (look into
org.mockito.runners). This means that junit is needed at compile time, and if a
user uses one of those classes, even at runtime. The point is that if a user
depends on mockito and uses one of those classes, he will also need to depend
on junit as well, that is probably why junit4 is not in Mockito's own
dependency list. The question here is: should we fix that? should we try to get
upstream to fix that?

/Roman

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.