[jira] [Commented] (SLING-8355) On first startup, ensure configurations become active immediately at the startlevel of org.apache.felix.configadmin

["Robert Munteanu (Jira)" <ji...@apache.org>]

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

Robert Munteanu commented on SLING-8355:
----------------------------------------

I think this shares the same root cause as SLING-7811, see especially the discussion starting with https://issues.apache.org/jira/browse/SLING-7811?focusedCommentId=16573007&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16573007 . In that issue we decided that working with the installer is not the way to go.

> 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
(v8.3.4#803005)