The first basic version of the implementation is available at 
https://github.com/kameshsampath/bnd/tree/subsystem-poc, right now I am struck 
at how to build the capabilities of the Subsystem-Content, in both the 
scenarios declerative as well as embedded esa files.

 -Kamesh
 


From: [email protected]
To: [email protected]
Subject: RE: Indexing Subsystem Bundles
Date: Wed, 7 Jan 2015 18:27:55 +0530




Hi David,
I was referring to your index.xml [1] and trying to update the bndtools/bnd by 
adding a ResourceAnalayzer for ESA, but I am not getting how to build the 
capabilities for ESA resource in R5 repo. How did you compute the capabilities 
for “osgi.wiring.package” and “osgi.service” ?

Regards,Kamesh
 







[1] https://github.com/bosschaert/devicemon/blob/master/devicemon-repo/index.xml

From: [email protected]
To: [email protected]
Subject: RE: Indexing Subsystem Bundles
Date: Tue, 6 Jan 2015 16:16:24 +0530




Thanks David.

Let me try updating the tools and the push the changes upstream.
  
Regards,
Kamesh 
 


> From: [email protected]
> Date: Tue, 6 Jan 2015 10:10:14 +0000
> Subject: Re: Indexing Subsystem Bundles
> To: [email protected]
> 
> Hi Kamesh,
> 
> I guess it would really be a matter of updating the bnd repo index
> tool [1] or the maven bundle plugin. AFAIK there is currently no
> ready-made tool that can do this yet. Both are open source, so more
> help is always appreciated I'm sure.
> 
> Best,
> 
> David
> 
> [1] https://github.com/bndtools/bnd/blob/master/REPOINDEX.md
> 
> On 31 December 2014 at 14:56, Kamesh Sampath <[email protected]> 
> wrote:
> > Hi,
> >
> > How can index the ESA bundles?  Currently we can index the normal OSGi
> > bundles using the Apache maven bundle plugin or using the bndtools indexing
> > tool.  But I dont see how I can index Subsystem archives *.esa.
> >
> > I was following David Bosschaert blog posts on Subsystems and download his
> > demo source, but unable to find the way of adding ESA to OBR.
> >
> >
> > Thank you.
> >
> >
> >
> > Regards,
> >
> > Kamesh
> >
> >
> >
                                                                                
                                          

Reply via email to