karaf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Jencks <david_jen...@yahoo.com.INVALID>
Subject Re: [karaf-boot] New plugin system POC
Date Thu, 12 May 2016 07:44:39 GMT
I don’t quite understand what you are trying to do, but…

You should write this as a bnd plugin.  Judging by the jpa sample you show I think the  (spec,
not bnd proprietary) dsannotations and metatypeannotations processors in bnd would be good
models to copy.  Both of these scan classes in the bundle under construction and generate
xml documents that go in the bundle and manifest headers from them.  I’m not sure if it’s
applicable to your use but Peter had this neat idea for a meta annotation that can be used
on third part annotations to add additional other-namespace attributes into the generated
document.  I use it (publicly) for the the felix ds extension attributes (DSExt annotation
in  the felix scr-ext-anno project.

david jencks

> On May 12, 2016, at 12:18 AM, Christian Schneider <chris@die-schneider.net> wrote:
> We currently use java annotation processors for out starters. The problem is that these
are not integrated with maven.
> So for example if we create files in the processors they will not be added to the resulting
> I have created a prototype of a new plugin system based on xbean finder and a karaf boot
plugin SPI in a new branch.
> See
> https://github.com/apache/karaf-boot/tree/boot-plugin
> The karaf-boot maven plugin uses xbean finder to scan for boot-plugins. Each boot plugin
can then define which trigger annotation it supports and will be called
> back with all classes in user code that are annotated with the respective annotation.
The plugin can then process the information and
> create files as well as define additional Manifest headers.
> Maven plugin
> https://github.com/apache/karaf-boot/blob/boot-plugin/tools/karaf-boot-maven-plugin/src/main/java/org/apache/karaf/boot/maven/GenerateMojo.java
> Boot-plugin spi
> https://github.com/apache/karaf-boot/blob/boot-plugin/starters/plugin-api/src/main/java/org/apache/karaf/boot/plugin/api/BootPlugin.java
> The JPA starter is currently the only starter that uses the SPI
> https://github.com/apache/karaf-boot/blob/boot-plugin/starters/karaf-boot-starter-jpa/src/main/java/org/apache/karaf/boot/jpa/impl/JpaProcessor.java
> The JPA sample shows how it works. I did not need to do any changes to the example
> https://github.com/apache/karaf-boot/tree/boot-plugin/samples/jpa
> A good thing in the new SPI is that the user code only depends on the plugin API it does
not need access to xbean finder. I think this approach could allow us to keep the user space
> free of our internal dependencies if we do it well.
> I talked to Guillaume about the new plugin mechanism. He would prefer to use a bnd plugin
for this. I am open to this but was not able to implement it
> in short term. The bnd API is a bit strange. Still bnd should also provide us with all
the features we need.
> The current code combines the headers of all plugins into a bnd file which is then given
to the maven-bundle-plugin. One thing that does not yet work is to
> also allow the user to override some settings in his own bnd file. bnd does not seem
to allow one such file override settings defined in another.
> I would be glad about any ideas how to make this work.
> Christian
> -- 
> Christian Schneider
> http://www.liquid-reality.de
> Open Source Architect
> http://www.talend.com

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message