My memory might play tricks on me, but I think when we started with
Sling we didn't use the default properties from Felix and therefore
started with duplicating that list.
I also think that we changed that a couple of years ago and we could now
use the Felix default properties - but we never changed the sling
properties and just kept them as is. Therefore there shouldn't be a need
for the duplicate list in Sling - not sure if you need to remove the
property or specify a placeholder that is then replaced by one of the
default properties.
In any case, this all is only relevant for Java 8, as there is no
default list for higher versions anymore. The framework is calculating
the packages based on the available modules for Java 9+. I don't know
the details though :)
Regards
Carsten
Am 28.07.2020 um 07:10 schrieb Konrad Windszus:
Hi,
Currently in
https://github.com/apache/sling-org-apache-sling-starter/blob/5f44b7f6c6b75e4cfd5574fb701c3e7eca8405ef/src/main/provisioning/launchpad.txt#L26
the default property "org.osgi.framework.system.packages" from
https://github.com/apache/felix-dev/blob/master/framework/src/main/resources/default.properties
is completely overwritten.
That leads to the fact that e.g. javax.activation is not exported among several
others.
Why is that?
Isn't there a better way to prevent individual packages from getting exported
instead of duplicated the package list from Felix and just removing some of
those?
Maintaining such a list in Sling seems overly complex (especially if
differences are so hard to spot).
But maybe I am just missing something....
WDYT?
Konrad
--
--
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org
