You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Georg Henzler (Jira)" <ji...@apache.org> on 2021/12/15 18:28:00 UTC
[jira] [Updated] (FELIX-6486) Support configuring scripted checks from JCR and stop exporting the util package
[ https://issues.apache.org/jira/browse/FELIX-6486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Georg Henzler updated FELIX-6486:
---------------------------------
Fix Version/s: healthcheck.generalchecks 3.0.0
> Support configuring scripted checks from JCR and stop exporting the util package
> --------------------------------------------------------------------------------
>
> Key: FELIX-6486
> URL: https://issues.apache.org/jira/browse/FELIX-6486
> Project: Felix
> Issue Type: Improvement
> Components: Health Checks
> Affects Versions: healthcheck.generalchecks 2.0.14
> Reporter: Georg Henzler
> Assignee: Georg Henzler
> Priority: Major
> Fix For: healthcheck.generalchecks 3.0.0
>
>
> Currently there is a [scripted check variant available in Sling|https://github.com/apache/sling-org-apache-sling-hc-support/blob/master/src/main/java/org/apache/sling/hc/support/impl/ScriptedHealthCheck.java) that relies on the exported util package. In a feature-model setup of a well-known product based on this stack, the util package is hidden via the API regions runtime (to limit the API surface of that product).
> Overall the easiest solution to allow scripted checks to be configured using JCR paths is to use a dynamic approach directly in Felix (reflection). That way the currently exported package org.apache.felix.hc.generalchecks.util can be removed - then the bundle version needs to be bumped to 3.0.0, but this is not problem because 99% of the users should be configuring the checks only.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)