|
||||||||
|
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 |
||||||||
|
||||||||
|
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 |
||||||||
Brett,
I've been trying out the initial OSGi support of Hibernate the last couple of days and it looks really good. Your client sample bundles helped me a lot (https://github.com/brmeyer/HibernateOSGi). However I had one question concerning the generated OSGi manifest of the hibernate-core module.
Because the manifest is auto-generated, it does not take into account "optional" dependencies of the hibernate-core module. E.g. the javax.validation and javax.security imports are not always necessary I believe. But because the manifest is auto-generated, we are required to have all dependencies available in our OSGi container.
More specifically, the following dependencies could be optional I believe:
javax.validation/validation-api/1.0.0.GA
org.hibernate/hibernate-validator/4.2.0.Final
org.jboss.spec.javax.security.jacc/jboss-jacc-api_1.4_spec/1.0.2.Final
javax.servlet/javax.servlet-api/3.0.1 (needed by jacc)
I forked the 4.2-osgi branch and updated the Gradle build file of hibernate-core to make the imports optional.
https://github.com/timpeeters/hibernate-orm
Is this something you might consider in the future?