[
https://issues.apache.org/jira/browse/SLING-9624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500713#comment-17500713
]
Karl Pauls commented on SLING-9624:
-----------------------------------
Right, that was the issue - we had bundles that have imports with version
ranges that assume the old package versioning sling did. Thats why I did
massage the exports of the system bundle to work with that and still pick up
the modules from the jvm where possible.
> Get rid of custom "org.osgi.framework.system.packages"
> ------------------------------------------------------
>
> Key: SLING-9624
> URL: https://issues.apache.org/jira/browse/SLING-9624
> Project: Sling
> Issue Type: Improvement
> Components: Starter
> Reporter: Konrad Windszus
> Priority: Major
> Fix For: Starter 13
>
>
> Instead of using a Sling specific "org.osgi.framework.system.packages"
> property
> (https://github.com/apache/sling-org-apache-sling-starter/blob/5f44b7f6c6b75e4cfd5574fb701c3e7eca8405ef/src/main/provisioning/launchpad.txt#L26)
> we should just rely on the Felix default
> (https://github.com/apache/felix-dev/blob/master/framework/src/main/resources/default.properties)
> to not miss to export all relevant packages for the different JREs
> compare with
> https://lists.apache.org/thread.html/r0aa3c02c38b5026e24684a00de3c6c8506e166334e77892ac2ee0ab3%40%3Cdev.sling.apache.org%3E.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
