[ 
https://issues.apache.org/jira/browse/SLING-8355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Georg Henzler updated SLING-8355:
---------------------------------
    Fix Version/s: Starter Content 1.0.4

> 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
>             Fix For: Starter Content 1.0.4
>
>
> 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