[
https://issues.jboss.org/browse/JBIDE-18798?page=com.atlassian.jira.plugi...
]
Snjezana Peco commented on JBIDE-18798:
---------------------------------------
{quote}
some of the hibernate plugins means what ? not all hibernate versions are the same. API
has changed, different features etc.
{quote}
I have tested the birt build with hibernate3_5.
{quote}
I'll merge the patch for now. But it might be worth looking into a solution where the
Birt plugin becomes independent of the Hibernate API and uses the SPI classes. The problem
also exists for the CDI plugin.
{quote}
I have created JBIDE-18805.
Exporting Hibernate API
-----------------------
Key: JBIDE-18798
URL:
https://issues.jboss.org/browse/JBIDE-18798
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: hibernate
Affects Versions: 4.3.0.Alpha1
Reporter: Snjezana Peco
Assignee: Koen Aers
The birt component uses the Hibernate API that was exported within the
org.hibernate.eclipse.libs plugin.
Since this plugin has been removed, there is no plugin exporting the Hibernate API.
Could you export the org.hibernate.* and javax.persistence package in any of the
org.jboss.tools.hibernateX_X plugins
(org.jboss.tools.hibernate3_5, for instance)?
Attached is a possible patch.
[~maxandersen]
{quote}
in all honesty - we don't want to export this api if we can avoid it. That is what
was causing all kinds of multiple version problems for us.
{quote}
We would export only one plugin that would be used in the compile time.
Another solution is to add the required libraries to the birt component.
{quote}
btw. I reckon this also fails in branch?
{quote}
The branch includes the org.hibernate.eclipse.libs plugin so there is no problem.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)