You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Georg Henzler (Jira)" <ji...@apache.org> on 2019/08/22 17:35:00 UTC

[jira] [Resolved] (SLING-8653) Noop version of bundles org.apache.sling.hc.core and org.apache.sling.hc.webconsole

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

Georg Henzler resolved SLING-8653.
----------------------------------
    Resolution: Fixed

> Noop version of bundles org.apache.sling.hc.core and org.apache.sling.hc.webconsole
> -----------------------------------------------------------------------------------
>
>                 Key: SLING-8653
>                 URL: https://issues.apache.org/jira/browse/SLING-8653
>             Project: Sling
>          Issue Type: Improvement
>          Components: Health Check
>            Reporter: Georg Henzler
>            Assignee: Georg Henzler
>            Priority: Major
>             Fix For: Health Check Core 2.0.0, Health Check webconsole 2.0.0
>
>
> When creating new runtimes (by e.g. using the Sling starter SLING-8343) the bundles org.apache.sling.hc.core and org.apache.sling.hc.webconsole can be just left out. However for existing instances (based on the legacy provisioning model), it would be handy to have noop versions of the bundles to allow "deactivating" the sling hc bundles (leaving only the felix bundles active)



--
This message was sent by Atlassian Jira
(v8.3.2#803003)