[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-6307) hibernate.ui.test depends on org.jmock
[
https://jira.jboss.org/browse/JBIDE-6307?page=com.atlassian.jira.plugin.s...
]
Nick Boldt commented on JBIDE-6307:
-----------------------------------
I saw two issues:
1. org.hibernate.eclipse.jdt.ui.test depends on some version of jmock; NOT included in
manifest.mf, and therefore Tycho doesn't know which test/mock framework to
use/resolve
This could be fixed (maybe) by simply adding a version # into the manifest.mf, as long as
Tycho can then find that version in one of the maven repos available to it.
2. org.hibernate.eclipse.console.test -- depends on 2.5.1 (according to manifest.mf). Also
includes jmock 2.5.1 IN the plugin when compiled.
Should these be 3rd party dependencies be moved into a central place so other components
can reuse them?
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