<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">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? <div><br></div><div>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).</div><div><div><br><div><div>On 27 oct. 2011, at 22:52, Kevin Pollet wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
<div>
Hi experts,
</div><div><br></div><div>IMHO, making Bean Validation ready for the modular world is a great thing! </div><div><br></div><div>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 <a href="http://felix.apache.org/site/apache-felix-maven-bundle-plugin-bnd.html">maven-bundle-plugin</a>. The advantage is that the api can be deployed in an OSGi container out of the box. For JBoss Modules the descriptor <span style="color: rgb(51, 51, 51); font-family: Arial, Helvetica, FreeSans, sans-serif; line-height: 17px; ">reside alongside its content but we can provide it.</span></div><div><br></div>
<div>WDYT?</div><div><br>--Kevin<br><br></div>
_______________________________________________<br>beanvalidation-dev mailing list<br><a href="mailto:beanvalidation-dev@lists.jboss.org">beanvalidation-dev@lists.jboss.org</a><br>https://lists.jboss.org/mailman/listinfo/beanvalidation-dev<br></blockquote></div><br></div></div></body></html>