On Wed, 2017-12-06 at 11:52 +0100, Konrad Windszus wrote: > I for sure don't want to block any release. So if we can release > Sling 10 soon that's great. > > I would still like to understand why it is hard to deploy the missing > dependencies for Java9 as additional bundles (with the according > require headers). Do you have concerns that it is hard to figure out, > which dependencies need to be added or is it hard to build OSGi > bundles out of those dependencies?
If we deploy bundles for those dependencies Java 9 should work out of the box, as the exported package lists are based on the modules available at runtime. However, the Java 8 package definitions are static, and we would get packages exported by both the system bundle and some other bundles with different versions. This is opening a can of worms, which sooner or later leads to use constraint violations and overall system fragility. The way out would be to either: 1. adjust the exported package lists for Java 8 2. deploy new bundles only for Java 9 1. is a risky proposition, especially since it can affect backwards compatibility 2. requires further work in the provisioning model, and maybe a bad idea to invest in since the feature model is hopefully close to complete. I'm open to trying out any of these, and maybe there's an option (3) that I've missed, but neither of these look simple to me. Thanks, Robert
