On Fri, 2022-03-04 at 15:25 +0100, Konrad Windszus wrote: > But please wait for > https://github.com/apache/sling-org-apache-sling-starter/pull/56 < > https://github.com/apache/sling-org-apache-sling-starter/pull/56> > being approved and merged, as not exporting OSGi R8 packages is not > nice. > Also I would like to squeeze > https://github.com/apache/sling-org-apache-sling-starter/pull/55 < > https://github.com/apache/sling-org-apache-sling-starter/pull/55> > into Sling 12 and mention both OSGi Core R8 compliance and DS 1.4 > compliance in the release notes at > https://github.com/apache/sling-site/blob/master/src/main/jbake/content/news/sling-12-released.md > < > https://github.com/apache/sling-site/blob/master/src/main/jbake/content/news/sling-12-released.md > >.
That works for me, thanks. I would also like to discuss the Composum situation ( https://issues.apache.org/jira/browse/SLING-11168 ). The situation is the following: On Windows, for certain users ( Stefan, also reported by Sergiu ) composum does not install properly. We have a fix which involves switching to content packages instead of bundles with initial content, but makes the startup much longer - probably from 10 seconds to 25. The problem does not appear with the Docker images. I see three posssible approaches: 1. Switch to content packages and accept the considerably slower startup 2. Diagnose the content loading problem and provide a fix in the content loader 3. Postpone the problem since it does not affect the recommended way of running the Starter *for our users*, which is Docker. I would incline to skip the fix for the Starter 12 release (3) and then find a solution for content loader (2). A second option would be switching to content pacakges (1) and the a fix for the content loader (2), but I think the quick startup time is something we should hold on to. Thoughts? Thanks, Robert
