On Apr 16, 2013, at 2:56 PM, Bill Burke <bburke@redhat.com> wrote:

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.

This may relate to the Provisioner service 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.

On 4/15/2013 4:37 AM, Thomas Diesler wrote:
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).

Perhaps you could explain (again) the motivating goal for your question.

cheers
--thomas

On Apr 12, 2013, at 4:46 PM, Bill Burke <bburke@redhat.com> wrote:

Is there any way we could get the OSGi bundles configured and deployed
as modules? I know David talked something about this earlier. We all
talked earlier about the maven artifact stuff I'm doing with JBoss
Modules, and the OSGI bundles are the only thing that I have excluded
from my JBoss AS build script that sets this up.
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev

xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
JBoss OSGi Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx

--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com