Having thought a bit more about this, for most bundles implementing a
health check it is more of an optional extension. This means bundle-XYZ
primarily will provide the functionality XYZ with an optional health
check testing state around functionality XYZ in action. Usually you
would even make the package dependency to org.apache.felix.hc.api
optional with the result that
- if bundle org.apache.sling.hc.api is *not* available,
functionality XYZ is still fully working
- if bundle org.apache.sling.hc.api *is* available,
functionality XYZ is working and can be checked via provided HC(s)
So I think it's fine to start without an explicitly declared capability,
we can add this easily later if desired.
-Georg
On 2019-01-21 15:06, Raymond Auge wrote:
On Mon, Jan 21, 2019 at 2:19 AM Georg Henzler <fe...@ghenzler.de>
wrote:
Hi Ray,
so your suggestion is more about referring to a capability like
"org.apache.felix.healthcheck" by using requirements in other bundles
than writing a health check that ensures the framework provides a
certain non-healthcheck-related capability.
Precisely,
- Ray
> I can probably try it out and submit the proper cap&req.
that would be great!
-Georg
