<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Apr 16, 2013, at 2:56 PM, Bill Burke <<a href="mailto:bburke@redhat.com">bburke@redhat.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">I'm trying to make a AS distribution that has no jars. Instead, metadata points to a maven repository location for those jars. I've patched Jboss Modules to make this work, but have no solution for OSGi.<br></blockquote><div><br></div>This may relate to the <a href="http://community.jboss.org/wiki/ProvisionerServiceAndFeatureDeployment">Provisioner service</a> topic. We already have a component that understands Maven coordinates and can provide named resources. If you are thinking of a special ModuleLoader that can fetch modules on demand then this loader should preferably simply call the Repository IMHO. In the near future it could call the Provisioner service with the top level Requirements.</div><div><br><blockquote type="cite"><br>David Lloyd said he didn't understand why your bundles weren't deployed as modules. I don't know what that means either, but that's what he said.<br></blockquote><div><br></div>Don't what this means either ;-) but I regularly talk with him so I can probably find out</div><div><br></div><div>cheers</div><div>--thomas </div><div><br><blockquote type="cite"><br>On 4/15/2013 4:37 AM, Thomas Diesler wrote:<br><blockquote type="cite">What do you mean? Bundle become modules when they get deployed at runtime. The reason that the 'bundles' directory exists is that the artefacts in there have their respective dependencies defined in standard OSGi metadata, which makes them bundles (i.e. a bundle cannot have a modules.xml file).<br><br>Perhaps you could explain (again) the motivating goal for your question.<br><br>cheers<br>--thomas<br><br>On Apr 12, 2013, at 4:46 PM, Bill Burke <<a href="mailto:bburke@redhat.com">bburke@redhat.com</a>> wrote:<br><br><blockquote type="cite">Is there any way we could get the OSGi bundles configured and deployed<br>as modules? I know David talked something about this earlier. We all<br>talked earlier about the maven artifact stuff I'm doing with JBoss<br>Modules, and the OSGI bundles are the only thing that I have excluded<br>from my JBoss AS build script that sets this up.<br>--<br>Bill Burke<br>JBoss, a division of Red Hat<br><a href="http://bill.burkecentral.com">http://bill.burkecentral.com</a><br>_______________________________________________<br>jboss-as7-dev mailing list<br>jboss-as7-dev@lists.jboss.org<br>https://lists.jboss.org/mailman/listinfo/jboss-as7-dev<br></blockquote><br>xxxxxxxxxxxxxxxxxxxxxxxxxxxx<br>Thomas Diesler<br>JBoss OSGi Lead<br>JBoss, a division of Red Hat<br>xxxxxxxxxxxxxxxxxxxxxxxxxxxx<br><br><br><br></blockquote><br>-- <br>Bill Burke<br>JBoss, a division of Red Hat<br><a href="http://bill.burkecentral.com">http://bill.burkecentral.com</a><br></blockquote></div><br><div>
<div><pre class="moz-signature" cols="72">xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
JBoss OSGi Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx </pre><div><br></div></div><br class="Apple-interchange-newline">
</div>
<br></body></html>