[jira] [Commented] (FELIX-5396) Move Sling annotations to dedicated artifact

["Stefan Seifert (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FELIX-5396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15636286#comment-15636286 ] 

Stefan Seifert commented on FELIX-5396:
---------------------------------------

and the separate bundle for the sling-only SCR annotations should be part of the sling project.
i suppose they are only part of the felix project because long time ago there was no possibility to add custom annotations via an SPI to the SCR generator.

and the sling SCR annotations may have be refactored on the way to use the same "style" as the new OSGi annotations. e.g. defining the properties with a string array attribut instead of separate @Property/@Properties annotations - otherwise you still need (part) of the Felix SCR annotations.

> Move Sling annotations to dedicated artifact
> --------------------------------------------
>
>                 Key: FELIX-5396
>                 URL: https://issues.apache.org/jira/browse/FELIX-5396
>             Project: Felix
>          Issue Type: Improvement
>          Components: SCR Tooling
>    Affects Versions: scr annotations 1.12.0
>            Reporter: Konrad Windszus
>            Priority: Minor
>
> Currently both the Felix SCR and the custom Sling annotations live in the same JAR. In my projects I don't want to use Felix SCR annotation since OSGi 6 defined now its own annotations for components and metatypes (being evaluated by bnd), but still the custom Sling annotations are useful. For that it would be helpful to just declare a dependency to the Sling annotations (and let them process with maven-scr-plugin or scr-bnd-plugin) without polluting my classpath with the Felix SCR annotations. Probably at the same time it makes more sense to maintain the Sling specific annotations and generator in Sling rather than in Felix.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)