[
https://issues.apache.org/jira/browse/SLING-5744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15298254#comment-15298254
]
Konrad Windszus commented on SLING-5744:
----------------------------------------
This is already supported and works correctly as being verified by
{{ConfigPrioritiesTest#testOverrideConfig}}. In my case the installer was just
stuck. The error went away after restarting the installer bundle. Since I
cannot reproduce the issue any longer I close this issue.
> OSGi Installer does not activate the right config after a more prioritized
> config gets deleted
> ----------------------------------------------------------------------------------------------
>
> Key: SLING-5744
> URL: https://issues.apache.org/jira/browse/SLING-5744
> Project: Sling
> Issue Type: Bug
> Components: Installer
> Affects Versions: Installer Core 3.6.4, JCR Installer 3.1.16
> Reporter: Konrad Windszus
>
> I have the following content in my repository
> {code}
> 1. /apps/configuration/config.<matchingrunmode1>/<myservice.pid>
> 2.
> /apps/configuration/config.<matchingrunmode1>.<matchingrunmode2/<myservice.pid>
> {code}
> The configuration 2. is correctly active now.
> I now remove the configuration in 2. (i.e. the node
> apps/configuration/config.<matchingrunmode1>.<matchingrunmode2/<myservice.pid>
> vanishes).
> The JcrInstaller is not correctly switching to the newly active configuration
> 1. but rather 2. stays active.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
