You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Konrad Windszus (JIRA)" <ji...@apache.org> on 2018/04/27 10:01:00 UTC

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

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

Konrad Windszus commented on FELIX-5396:
----------------------------------------

This is now tracked in SLING-7624.

> 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
(v7.6.3#76005)