You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (Jira)" <ji...@apache.org> on 2021/07/21 09:17:00 UTC
[jira] [Commented] (SLING-10648) API Regions: Support exposing a
package but preventing extending classes or implementing interfaces from it
[ https://issues.apache.org/jira/browse/SLING-10648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17384768#comment-17384768 ]
Carsten Ziegeler commented on SLING-10648:
------------------------------------------
I think annotations on a class level are sufficient to mark the usage per interface; If the whole package has the same usage pattern, then why isn't applying the class anotations on every class enough?
> API Regions: Support exposing a package but preventing extending classes or implementing interfaces from it
> -----------------------------------------------------------------------------------------------------------
>
> Key: SLING-10648
> URL: https://issues.apache.org/jira/browse/SLING-10648
> Project: Sling
> Issue Type: Improvement
> Components: Feature Model
> Affects Versions: Feature Model API Regions Extension 1.3.6
> Reporter: Konrad Windszus
> Priority: Major
>
> In some cases certain packages expose API interfaces which should not be implemented by any bundles outside the API region but still be exported for regular usage.
> This is similar to the annotation {{@ProviderType}} or {{@noimplement}} and {{@noextend}} from [Eclipse PDE|https://wiki.eclipse.org/PDE/API_Tools/Restrictions] but allows restricting to a certain context.
> This is triggered by the discussion in https://github.com/Adobe-Consulting-Services/acs-aem-commons/issues/2648.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)