[
https://jira.jboss.org/browse/JBIDE-6307?page=com.atlassian.jira.plugin.s...
]
Vitali Yemialyanchyk commented on JBIDE-6307:
---------------------------------------------
jmock works here good, it is easy to use, i.e. it did his work - mock objects and give
possibility to test particular functionality.
There is no sence to switch to some other mock library, particulary for existing tests.
I did not know which mock library be preferable for others jboss tool team members, now
there is no common point of view here, as I know.
Where was not such point of view 1.5 year ago when I wrote these tests.
In any case there is no sense to move this jars into common. Hibernate Tools part has no
dependence from common, no sence to add dependence for the test part. No sence to rewrite
tests.
From the issue description I can't understand what is wrong with
jmocks?
hibernate.ui.test depends on org.jmock
--------------------------------------
Key: JBIDE-6307
URL:
https://jira.jboss.org/browse/JBIDE-6307
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Hibernate
Affects Versions: 3.2.0.M2
Reporter: Nick Boldt
Assignee: Vitali Yemialyanchyk
Priority: Blocker
Fix For: 3.2.0.Beta
I assume for this we'll need to add jmock into a plugin which can expose these
dependencies as libraries on the classpath... perhaps a new plugin in tests/ or common/ ?
To add support for jmock via Maven, you apparently need only add a few things into the
parent pom:
http://www.jmock.org/maven.html
I've briefly prototyped this but currently can't get hibernate to build due to
upstream component build failures.
Worthy of note, the Teiid/Modeshape guys are playing with Mockito, rather than jMock.
Perhaps we need to settle on ONE framework for mocking?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira