So all JARs must be OSGi-ified before they can be used? Is there any way to keep this information outside? Do you know of any other JSR published JAR that also expose its OSGi headers? 

I'm asking because declaring dependencies means that all dependent JSRs (and the JDK) will need to be OSGi-ified as well. I'd rather see that coordinated by the Java EE expert group. There is also the problem of supporting them forever(tm).

On 27 oct. 2011, at 22:52, Kevin Pollet wrote:

Hi experts,

IMHO, making Bean Validation ready for the modular world is a great thing! 

A first step might be to provide the module meta-datas (OSGi headers, …). For OSGi, those meta-datas can be added to the jar Manifest within the maven build with the maven-bundle-plugin. The advantage is that the api can be deployed in an OSGi container out of the box. For JBoss Modules the descriptor reside alongside its content but we can provide it.

WDYT?

--Kevin

_______________________________________________
beanvalidation-dev mailing list
beanvalidation-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/beanvalidation-dev