On Thursday 30 July 2015 08:29:24 Carsten Ziegeler wrote: > Am 29.07.15 um 23:02 schrieb Oliver Lietz: > > Radu, > > > > the issue is fixed, but I really don't like the use of the startup handler > > from org.apache.sling.launchpad.karaf in contentloader as this will block > > a > > release until I finally release it. > > We should come up with a generic startup handler _finally_ or use a simple > > dummy in the tests. > > What is it used for in the tests?
It's to satisfy Sling Settings (Sling ID is used by content loader). And if there is no startup handler, the JCR isn't setup properly (missing folders). This behavior crept in after Sling 6. Regards, O. > Carsten
