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

Eric Norman commented on SLING-11141:
-------------------------------------

[~henzlerg] Thanks for your feedback.  I had also considered marking the 
ScriptedHealthCheck in this bundle as deprecated and just forward all the calls 
to the Felix equivalent, but getting the forwarding logic to work was somewhat 
complicated.  Also, I did see that the ScriptedHealthCheck in this bundle is 
not 100% compatible with the felix impl due to the reason I described in my 
comment to Oliver above.  But since I don't have much insight as to how people 
are using this, I decided to take the safe approach and leave this 
ScriptedHealthCheck in place but I do not have a firm opinion on that.

Do you see any of your deprecation concerns as blockers for the release of the 
1.0.8 version that is already underway?  Or can these be addressed in the next 
release?

> Make compatible with org.apache.felix.healthcheck.generalchecks version 3.x
> ---------------------------------------------------------------------------
>
>                 Key: SLING-11141
>                 URL: https://issues.apache.org/jira/browse/SLING-11141
>             Project: Sling
>          Issue Type: Bug
>            Reporter: Eric Norman
>            Assignee: Eric Norman
>            Priority: Major
>             Fix For: Health Check Support 1.0.8
>
>          Time Spent: 2h 50m
>  Remaining Estimate: 0h
>
> After updating to the org.apache.felix.healthcheck.generalchecks version 
> 3.0.0 release, the org.apache.sling.hc.support bundle fails during the 
> feature analyzer with this error:
> {noformat}
> [ERROR] [bundle-packages] org.apache.sling:org.apache.sling.hc.support:1.0.6: 
>  is importing package(s) org.apache.felix.hc.generalchecks.util in start 
> level 20 but no bundle is exporting these for that start level.
> {noformat}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to