[
http://opensource.atlassian.com/projects/hibernate/browse/HV-267?page=com...
]
Jaro Kuruc commented on HV-267:
-------------------------------
I just got your point with regards to non-shaded v. shaded jar and the package names.
May I raise a question why there is a need to shade JType packages? This kind of goes
against the OSGi principle, because it makes it impossible to switch implementations at
runtime (like using bug-fixed version, etc.), just like it is possible with SLF4J and JPA
as a matter of fact.
Can you please advocate why is JType not just another runtime lib, just like SLF4J?
Especially now, that JType is in Central M2 repo
(
http://repo2.maven.org/maven2/com/googlecode/jtype/jtype) and there's a newer version
available (0.1.1).
Enhance distribution jar to make it OSGi bundle
-----------------------------------------------
Key: HV-267
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HV-267
Project: Hibernate Validator
Issue Type: Improvement
Components: build
Affects Versions: 4.0.1.GA
Reporter: Jaro Kuruc
Fix For: 4.1.0
Attachments: maven-bundle-plugin.patch
Hi, please consider enhancing validator's maven build to produce OSGi compliant
bundle by adding OSGi specific manifest headers. At the moment, there are 2 options to do
that:
1. Felix Bundle Plugin
http://felix.apache.org/site/apache-felix-maven-bundle-plugin-bnd.html
2. SpringSource Bundlor
http://static.springsource.org/s2-bundlor/1.0.x/user-guide/html/ch03s03.html
Also, take a look at the bundle which has been produced by SpringSource
http://www.springsource.com/repository/app/bundle/version/detail?name=com...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira