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 2015/01/19 18:25:34 UTC

[jira] [Commented] (FELIX-4170) Deprecate inheritance of component descriptors

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

Konrad Windszus commented on FELIX-4170:
----------------------------------------

What about not deprecating the attribute fully, but only log a warning in case the parent of a OSGi component is not defined in the same Maven module? I guess in this case you should never run into runtime problems.

> Deprecate inheritance of component descriptors
> ----------------------------------------------
>
>                 Key: FELIX-4170
>                 URL: https://issues.apache.org/jira/browse/FELIX-4170
>             Project: Felix
>          Issue Type: Task
>          Components: SCR Tooling
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>             Fix For: maven-scr-plugin 1.14.0, scr ant task 1.8.0, scr generator 1.8.0, scr annotations 1.9.6
>
>
> The inheritance feature of the annotations is problematic as this only works reliable if the super class used at build time is the same as at run time. However at the point of descriptor generation this can't be ensured and therefore might lead to subtle problems.
> In addition, the DS spec decided against inheritance for the same reasons.
> Therefore it is advisable to remove this feature in the long run. As a first step we should log a warning if inheritance is used



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