[ 
https://issues.apache.org/jira/browse/SLING-8355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16839465#comment-16839465
 ] 

Georg Henzler commented on SLING-8355:
--------------------------------------

Made the sling starter startup index.html file available via content bundle 
org.apache.sling.starter.content in 
[102e4d94f1bc27dffe|https://gitbox.apache.org/repos/asf?p=sling-org-apache-sling-starter-content.git;a=commitdiff;h=c2c921953624701424f44291f5285ad70c1496f1;hp=102e4d94f1bc27dffeb6c50c724481f4fafbe964]

> On first startup, ensure configurations become active immediately at the 
> startlevel of org.apache.felix.configadmin
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: SLING-8355
>                 URL: https://issues.apache.org/jira/browse/SLING-8355
>             Project: Sling
>          Issue Type: Improvement
>            Reporter: Georg Henzler
>            Priority: Major
>
> On first startup the configurations currently become active only at start 
> level 30, on subsequent startups have the configurations active when 
> org.apache.felix.configadmin ist started. This shall be changed in a way that 
> also on first startup configurations get active as soon as possible (once 
> org.apache.felix.configadmin is active)
> See 
> https://lists.apache.org/thread.html/e243977448efb65c401f1ea0341533906ac0e8cc4af1dfa59945e5f5@%3Cdev.sling.apache.org%3E



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to