[
https://issues.apache.org/jira/browse/SLING-7569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16426602#comment-16426602
]
Konrad Windszus commented on SLING-7569:
----------------------------------------
The code responsible for this is in
https://github.com/apache/sling-org-apache-sling-installer-hc/blob/6de934ee71fb1fa065e095806a2b31a60bafd141/src/main/java/org/apache/sling/installer/hc/OsgiInstallerHealthCheck.java#L153
> Also warn in case if only one of the supplied bundles/configurations 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 1.0.2
>
>
> 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)
