David,

>From my understanding (and from your blog posts) the subsystem spec is
part of OSGi R5. I¹m on a version of Felix < 4.4.0. I¹m assuming there is
no option to use this then without upgrading the system bundle, is that
right?

Thanks!
Derek Abdine

On 3/17/14, 2:06 PM, "David Bosschaert" <[email protected]> wrote:

>Hi Derek,
>
>On 17 March 2014 11:21, Derek Abdine <[email protected]> wrote:
>> Hm this is fantastic, thanks David (both for the note here and for your
>> contribution by way of the blog post)! Seems mostly in-line with what
>>I'm
>> looking for. Correct me if I'm wrong, but this seems also like the
>> OSGi-standard way of approaching what Apache Karaf calls features in
>>their
>> provisioning model. Is that right?
>
>Yep, this is the standard way to do it and it was influenced by Apache
>Karaf features, Spring Plans, Aries 'applications', Eclipse features
>and other similar technologies.
>
>> If I may ask -- is there good tooling support for automating the
>>creation
>> of .esa files? I use a maven toolchain in-house so something such as the
>> karaf-maven-plugin and it's ability to generate feature files from Maven
>> poms would be highly valuable.
>
>There is some tooling for it in terms of the ESA Maven Plugin at
>Apache Aries (http://aries.apache.org/modules/esamavenpluginproject.html).
>I think the tooling could be improved, but in the end an ESA file is
>just a zip file and the SUBSYSTEM.MF file is just a text file, so you
>could use any tools that can produce these as well.
>
>Cheers,
>
>David
>_______________________________________________
>OSGi Developer Mail List
>[email protected]
>https://mail.osgi.org/mailman/listinfo/osgi-dev

This electronic message contains information which may be confidential or 
privileged. The information is intended for the use of the individual or entity 
named above. If you are not the intended recipient, be aware that any 
disclosure, copying, distribution or use of the contents of this information is 
prohibited. If you have received this electronic transmission in error, please 
notify us by e-mail at ([email protected]) immediately.

_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev

Reply via email to