[ https://issues.jboss.org/browse/JBIDE-12971?page=com.atlassian.jira.plugi... ] Paul Richardson commented on JBIDE-12971: ----------------------------------------- [~mickael_istria] It all hinges on use fragments as tests. I did investigate Eclipse's buddy policy right at the start. I cannot remember precisely the reason for it not working but I think it relates to the following: * The mockito bundle would need to declare a buddy policy of some kind in its manifest, eg. registered; * EVERY test fragment would have to include the modified configuration class * I think it is also impossible to declare a buddy policy on the fragment (I could be wrong!). If this is the case then the host plugin would require the buddy policy and then that plugin is declaring a buddy policy with a test framework, architecturally wrong and (again my memory is faillible!) with fail at runtime with classpath issues if mockito is not present. As for using fragments Fragments cannot depend on fragments. I was asked this on the on the mockito [list|https://groups.google.com/d/msg/mockito/eLE186uE0uc/o3_OIwpUoP8J] as well. -- 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