[
https://issues.apache.org/jira/browse/SLING-12026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17784410#comment-17784410
]
Carsten Ziegeler edited comment on SLING-12026 at 11/9/23 12:16 PM:
--------------------------------------------------------------------
I don't have a good idea; I have the feeling that the feature analyser is
probably the wrong place to do this check. It could be easily done in the maven
plugin by checking the dependencies for the provider list files
Even with SLING-12084 implemented (adding that info to the feature model), the
analyser can not distinguish between bundles where it might be allowed to
implement a provider type and a bundle where it is not allowed. So I think that
logic needs to be somewhere else where more context is available.
was (Author: cziegeler):
I don't have a good idea; I have the feeling that the feature analyser is
probably the wrong place to do this check. It could be easily done in the maven
plugin by checking the dependencies for the provider list files
> Check for implementation/extension of provider types
> ----------------------------------------------------
>
> Key: SLING-12026
> URL: https://issues.apache.org/jira/browse/SLING-12026
> Project: Sling
> Issue Type: New Feature
> Components: Feature Model Analyser
> Affects Versions: Feature Model Analyser 2.0.0
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Priority: Major
>
> OSGi distinguishes between
> [consumer|https://docs.osgi.org/javadoc/osgi.annotation/7.0.0/org/osgi/annotation/versioning/ConsumerType.html]
> and
> [provider|https://docs.osgi.org/javadoc/osgi.annotation/7.0.0/org/osgi/annotation/versioning/ProviderType.html]
> types (either interfaces or classes).
> Some bundles/features are only supposed to implement/extend consumer types in
> order to be more stable against API changes. There should be a feature model
> analyser enforcing this.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
