Message Title

@gsmet I see, although wondering why the redirect artefact would be identical to the actual location, but without the OSGi headers.

I tried the latest 6.0.2 version btw. The symbolic name is now correct, but the fragment is still ignored by Felix. Removing the fragment from the OSGi headers results in:

org.osgi.framework.BundleException: Unresolved constraint in bundle org.hibernate.validator.hibernate-validator-cdi [125]: Unable to resolve 125.0: missing requirement [125.0] osgi.wiring.package; (&(osgi.wiring.package=org.hibernate.validator.internal.engine)(version>=6.0.2.Final)(version<=6.0.2.Final))
	at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:3974)
	at org.apache.felix.framework.Felix.loadBundleClass(Felix.java:1824)
	at org.apache.felix.framework.BundleImpl.loadClass(BundleImpl.java:937)
	at org.jvnet.hk2.osgiadapter.OSGiModuleImpl$4$1.run(OSGiModuleImpl.java:432)
	at org.jvnet.hk2.osgiadapter.OSGiModuleImpl$4$1.run(OSGiModuleImpl.java:429)
	at java.security.AccessController.doPrivileged(Native Method)
	at org.jvnet.hk2.osgiadapter.OSGiModuleImpl$4.loadClass(OSGiModuleImpl.java:429)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
	at com.sun.enterprise.v3.server.APIClassLoaderServiceImpl$APIClassLoader.loadClass(APIClassLoaderServiceImpl.java:260)