[
https://issues.apache.org/jira/browse/KARAF-7950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18001236#comment-18001236
]
ASF subversion and git services commented on KARAF-7950:
--------------------------------------------------------
Commit b5223964733da2c8444d5a61d9bac87128112a6a in karaf's branch
refs/heads/karaf-4.4.x from Robert Varga
[ https://gitbox.apache.org/repos/asf?p=karaf.git;h=b522396473 ]
[KARAF-7950] Use modular OSGi dependencies
osgi-core is non-modular, i.e. it has no Automatic-Module-Name
declaration.
This patches switches to using org.osgi.{dto,framework,resource,...},
which are provide this stability.
Signed-off-by: Robert Varga <[email protected]>
(cherry picked from commit e62f7cb4c4001421ad6128e731622b202feed88e)
> Use modular OSGi dependencies
> -----------------------------
>
> Key: KARAF-7950
> URL: https://issues.apache.org/jira/browse/KARAF-7950
> Project: Karaf
> Issue Type: Improvement
> Reporter: Robert Varga
> Assignee: Jean-Baptiste Onofré
> Priority: Major
>
> As we move past Java 8, we need to look towards JPMS modules. That world is
> not supported by osgi.core/osgi.cmpn/osgi.annotation, but rather a set of
> broken-out bundles, each carrying Automatic-Module-Name. That header is
> critical to downstreams who provide module-info.java, as it provides a stable
> module name for the purposes of 'requires'.
> Convert users of 'osgi.core' using karaf-bom to use its replacements, like
> org.osgi.framework, org.osgi.util.tracker, etc.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
