[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-6307) hibernate.ui.test depends on org.jmock

[Vitali Yemialyanchyk (JIRA)]

    [ https://jira.jboss.org/browse/JBIDE-6307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12542950#action_12542950 ] 

Vitali Yemialyanchyk commented on JBIDE-6307:
---------------------------------------------

org.hibernate.eclipse.jdt.ui.test depends on org.hibernate.eclipse.console.test.

Nick, I do not understand the problem so I can't help to fix it. If add version info into manifest fix the server build problem, please, add this info.

Currently all hibernate mock tests depends on jmock 2.5.1. But in manifest there are only references to jmock jars, once again - it possible to get rid of versions numbers in path and name - so manifest will not point to concret version of jmock, i.e. from manifest will not be possible to guess, which is jmock version we are using.

No. I don't think we should move jmocks jar to some central place. The libs should stay in same place, just possible to rename "jmock-2.5.1" folder to "jmock", "jmock-2.5.1.jar" to "jmock.jar" and same for others jars.


> 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