[
https://issues.jboss.org/browse/JBIDE-12971?page=com.atlassian.jira.plugi...
]
Paul Richardson commented on JBIDE-12971:
-----------------------------------------
[~adietish]
The 1.9.5 version of Mockito has a couple of configuration options, which can be set
using an external class that implements IMockitoConfiguration. This setup does not work in
Eclipse plugins due to the separate plugin classloaders. Thus, the patch adds in a
MockitoConfiguration class that makes the configuration options publicly settable.
The specific configuration option that this change addressed was to disable a cache that
mockito uses for classes. The cache hashes classes based on their package.class name,
which is problematic if 2 different plugins running tests have the same package.class
name. This may or may not be applicable to your setup.
Thus, in most environments the patch is irrelevant and mockito will behave as the default
1.9.5 version.
Add mockito to the TP
---------------------
Key: JBIDE-12971
URL:
https://issues.jboss.org/browse/JBIDE-12971
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: build
Affects Versions: 4.0.0.Beta1
Reporter: Andre Dietisheim
Assignee: Mickael Istria
Fix For: 4.2.x
It would be great if we could use mockito (
http://code.google.com/p/mockito/) in our
tests. We would have to add it to our target platform (TP) for our plugins to use it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira