Hi Carsten, thanks for your answer. One other thing to mention here is that custom plugins exist for the maven-scr-plugin (http://felix.apache.org/documentation/subprojects/apache-felix-maven-scr-plugin/extending-scr-annotations.html <http://felix.apache.org/documentation/subprojects/apache-felix-maven-scr-plugin/extending-scr-annotations.html>). Could those be easily migrated to bnd plugins? Do you have any hints on how to accomplish that for @SlingServlet, @SlingFilter (currently part of maven-scr-plugin, but should be moved to a Sling module then) and for @SlingHealthCheck (https://github.com/apache/sling/blob/trunk/bundles/extensions/healthcheck/annotations/src/main/java/org/apache/sling/hc/annotations/SlingHealthCheckProcessor.java <https://github.com/apache/sling/blob/trunk/bundles/extensions/healthcheck/annotations/src/main/java/org/apache/sling/hc/annotations/SlingHealthCheckProcessor.java>)? Thanks Konrad
> On 07 Oct 2015, at 18:18, Carsten Ziegeler <[email protected]> wrote: > > Hi > > Am 07.10.15 um 21:07 schrieb Konrad Windszus: >> Hi, >> I am wondering about the future of the maven-scr-plugin. I think it should >> be deprecated and instead the documentation should point to the >> maven-bundle-plugin to be used now even for generating descriptors for >> metatype and declarative services. >> >> That can nowadays take care of generating the component descriptor [0] with >> the OSGi standard annotations [1]. For the metatype generation bnd came up >> with its own annotations[3], which should be a replacement for all >> maven-scr-plugin annotations. > Actually there are standard metatype annotations as well which work > nicely with the new R6 DS annotations. So no need to use proprietary > annotations anymore > >> Also it seems that maven-scr-plugin is not compatible with Declarative >> Services 1.3 (meaning I cannot use "Configuration Property Types”) [3]. > It only supports DS upto 1.2 > >> >> The only thing which is not covered in the maven-bundle-plugin is component >> inheritance (but that is deprecated anyways [4]). > That's why we deprecated it :) > >> Are there any other feature of the maven-scr-plugin which are not covered by >> bnd/maven-bundle-plugin? > Nearly none - we have default properties in the scr plugin, so you can > configure something like the vendor once in your parent pom and it gets > applied to every component. > > The plan is to indeed phase out the maven scr plugin. It still has some > usage, as the bundle plugin is not a dropin replacement. You would need > to rewrite your components - and switching to the official annotations > has some subtle differences in the defaults. > On the other hand, we have a bnd plugin that is able to process the > proprietary Felix annotations. > > Therefore, I totally agree that we should update the documentation. But > of course we have to support our user base for some time. > > Carsten > >> >> My request originates from the discussion at >> https://github.com/bndtools/bnd/issues/999. >> >> WDYT? >> Thanks for any input, >> Konrad >> >> >> [0] - http://www.aqute.biz/Bnd/Components >> [1] - >> https://osgi.org/javadoc/r6/enterprise/org/osgi/service/component/annotations/package-summary.html >> [2] - http://www.aqute.biz/Bnd/MetaType >> [3] - http://njbartlett.name/2015/08/17/osgir6-declarative-services.html >> [4] - https://issues.apache.org/jira/browse/FELIX-4170 >> >> > > > -- > Carsten Ziegeler > Adobe Research Switzerland > [email protected]
