[
https://issues.apache.org/jira/browse/FELIX-6486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17460149#comment-17460149
]
Georg Henzler commented on FELIX-6486:
--------------------------------------
Implemented via
https://github.com/apache/felix-dev/commit/37c7c4e4e6ffeea9f177113dae41af00704f1088
> 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
>
> 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)
