You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Konrad Windszus (JIRA)" <ji...@apache.org> on 2018/04/11 07:41:00 UTC

[jira] [Closed] (SLING-7569) Also warn in case if only one of the supplied bundles/configurations within a group below the configured paths are valid

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

Konrad Windszus closed SLING-7569.
----------------------------------

> Also warn in case if only one of the supplied bundles/configurations within a group below the configured paths are valid
> ------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SLING-7569
>                 URL: https://issues.apache.org/jira/browse/SLING-7569
>             Project: Sling
>          Issue Type: Improvement
>          Components: Installer
>    Affects Versions: Installer Health Checks 1.0.0
>            Reporter: Konrad Windszus
>            Assignee: Konrad Windszus
>            Priority: Major
>             Fix For: Installer Health Checks 2.0.0
>
>
> Currently the OSGI Installer Health Check (contributed with SLING-5888) does not emit a warning in case there is one config not installed, if another one with the same PID is installed below /apps. 
> Since the runmode specifics are checked, before the artifact is put to the OSGi installer we should also warn if there are multiple artifacts of the same ID (PID/Bundle Symbolic Name) below the given checked folder as this is almost always a mistake which should be fixed.



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