This is an automated email from the ASF dual-hosted git repository.
kwin pushed a commit to branch master
in repository
https://gitbox.apache.org/repos/asf/sling-org-apache-sling-providertype-bnd-plugin.git
The following commit(s) were added to refs/heads/master by this push:
new 83648b9 Add remarks to README
83648b9 is described below
commit 83648b9fa54b1be5ce374a82d91f453e22f386fb
Author: Konrad Windszus <[email protected]>
AuthorDate: Sat Dec 23 15:46:24 2023 +0100
Add remarks to README
---
readme.md | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/readme.md b/readme.md
index b1af77e..f67c516 100644
--- a/readme.md
+++ b/readme.md
@@ -65,6 +65,11 @@ Multiple attributes must be separated with `;` according to
[OSGi Common Header
The information whether a type (i.e. a class or interface) is designed to be
extended/implemented only by providers or also by consumers is determined
originally from the the annotations
[`@org.osgi.annotation.versioning.ProviderType`][provider-type] or
[`@org.osgi.annotation.versioning.ConsumerType`][consumer-type].
In order to speed up the check [the annotation is evaluated and extracted into
a dedicated JSON file named `META-INF/api-info.json` when generating the apis
jar][api-info.json] and being looked up from there within this plugin. Only as
fallback and on demand this plugin evaluates the annotations from the classpath
directly.
+### Remarks
+
+All provider type annotations are not inherited, i.e. only the direct super
class and directly implemented interfaces are ever evaluated ([OSGi issue
#634](https://github.com/osgi/osgi/issues/643)).
+Bnd does not correctly calculate the proper import-package version policy for
provider type classes being extended ([Bnd issue
#5925](https://github.com/bndtools/bnd/issues/5925)).
+
[bnd-plugins]: https://bnd.bndtools.org/chapters/870-plugins.html
[provider-type]:
https://docs.osgi.org/javadoc/osgi.annotation/8.0.0/org/osgi/annotation/versioning/ProviderType.html
