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

["Georg Henzler (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SLING-8653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16913521#comment-16913521 ] 

Georg Henzler commented on SLING-8653:
--------------------------------------

Pushed https://github.com/apache/sling-org-apache-sling-hc-core/tree/noop-version-for-felix-migration and https://github.com/apache/sling-org-apache-sling-hc-webconsole/tree/noop-version-for-felix-migration with version 2.0.0 (although there are no packages exported with semantic versioning, a major version bump makes sense here as everything changes, also this allows to potentially release a 1.x version from maintenance branch if really needed)

> 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 webconsolee 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)