You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Dominik Süß (JIRA)" <ji...@apache.org> on 2018/10/12 13:31:05 UTC
[jira] [Resolved] (SLING-8010) Flaw when executionplans are
configured as empty in packageinit
[ https://issues.apache.org/jira/browse/SLING-8010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dominik Süß resolved SLING-8010.
--------------------------------
Resolution: Fixed
> Flaw when executionplans are configured as empty in packageinit
> ---------------------------------------------------------------
>
> Key: SLING-8010
> URL: https://issues.apache.org/jira/browse/SLING-8010
> Project: Sling
> Issue Type: Bug
> Components: Installer
> Reporter: Dominik Süß
> Priority: Major
>
> While adding a bit more test coverage I noticed that there is a refactoring flaw in the code not handling the case well where packageinit should skip when no executionplan is configured.
> The background is that an early draft was based on ConfigurationPolicy where this SlingRepositoryInitializer Service is supposed to always be active but skip in case there is nothing to install.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)