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

Konrad Windszus commented on SLING-12026:
-----------------------------------------

Are you referring to a specific Maven plugin where this could be easily done? I 
was more thinking about implementing a [bnd 
plugin|https://bnd.bndtools.org/chapters/870-plugins.html]. When using in the 
analyser you indeed need to distinguish between privileged and non-privileged 
bundles. But usually this is achieved by building separate features and only 
merging them afterwards (compare with 
https://github.com/adobe/aemanalyser-maven-plugin/blob/d2b7b530fb1ac8b0280c6c33560adedbcdb580f2/aemanalyser-core/src/main/java/com/adobe/aem/analyser/AemAnalyser.java#L70).
 What is the feature extension with name "api-jars-config" 
(https://github.com/apache/sling-org-apache-sling-feature-analyser/blob/e72bc7979b7d3de57dc538815fb7ef9fd27fb1d3/src/main/java/org/apache/sling/feature/analyser/task/impl/CheckApisJarsProperties.java#L65)
 referring to. Can that be used/extended somehow?

> 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)

Reply via email to