You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mrunit.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2014/05/06 23:58:31 UTC
[jira] [Commented] (MRUNIT-208) mrunit unnecessarily depends on
mockito-all
[ https://issues.apache.org/jira/browse/MRUNIT-208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13991202#comment-13991202 ]
Hudson commented on MRUNIT-208:
-------------------------------
FAILURE: Integrated in mrunit-trunk #1119 (See [https://builds.apache.org/job/mrunit-trunk/1119/])
MRUNIT-208: mrunit unnecessarily depends on mockito-all (Alexandre Normand via Dave Beech) (dbeech: rev 432b2441d85490f0867ae066bb76c0a122d1f5d6)
* pom.xml
> mrunit unnecessarily depends on mockito-all
> -------------------------------------------
>
> Key: MRUNIT-208
> URL: https://issues.apache.org/jira/browse/MRUNIT-208
> Project: MRUnit
> Issue Type: Improvement
> Reporter: Alexandre Normand
> Assignee: Alexandre Normand
> Priority: Minor
> Fix For: 1.1.0
>
> Attachments: MRUNIT-208.patch
>
>
> mrunit depends on mockito but it brings it in as {{mockito-all}}. {{mockito-all}} bundles {{hamcrest}} with it and makes it harder for downstream projects to manage/analyse their dependencies cleanly.
> I suggest that, to be a good citizen, mrunit declares explicit dependencies on {{mockito-core}} instead as well as a {{test}} scoped dependency on {{hamcrest-core}}.
--
This message was sent by Atlassian JIRA
(v6.2#6252)