[
https://issues.apache.org/jira/browse/HADOOP-14178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16085773#comment-16085773
]
Andras Bokor commented on HADOOP-14178:
---------------------------------------
FYI,
{{mvn javadoc:test-javadoc}} goal generates errors because we use mockito-all.
mockito-all includes Hamcrest classes but a different version. Let's see
{{TestReflectionUtils}} as an example:
{{import static org.hamcrest.CoreMatchers.containsString;}} will result in
error.
Somehow {{mvn javadoc:test-javadoc}} will find Mockito's {{CoreMatchers}} class
on the classpath which has no {{containsString}} method.
I did not raise new JIRA for this since from Mockito 2 the mockito-all is
discontinued so this ticket will solve this.
Any way I can help on this?
> Move Mockito up to version 2.x
> ------------------------------
>
> Key: HADOOP-14178
> URL: https://issues.apache.org/jira/browse/HADOOP-14178
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: test
> Affects Versions: 2.9.0
> Reporter: Steve Loughran
> Assignee: Akira Ajisaka
>
> I don't know when Hadoop picked up Mockito, but it has been frozen at 1.8.5
> since the switch to maven in 2011.
> Mockito is now at version 2.1, [with lots of Java 8
> support|https://github.com/mockito/mockito/wiki/What%27s-new-in-Mockito-2].
> That' s not just defining actions as closures, but in supporting Optional
> types, mocking methods in interfaces, etc.
> It's only used for testing, and, *provided there aren't regressions*, cost of
> upgrade is low. The good news: test tools usually come with good test
> coverage. The bad: mockito does go deep into java bytecodes.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
