[
https://issues.apache.org/jira/browse/SLING-2567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13437891#comment-13437891
]
Bertrand Delacretaz commented on SLING-2567:
--------------------------------------------
The dependency graph is
org.apache.felix.configadmin -> org.apache.felix.http.jetty ->
org.apache.sling.installer.core (imports the javax.servlet package)
so it is indeed correct to reactivate installer.core when configadmin is
refreshed, but the isInstallerBundleAffected() method does not detect this
transitive dependency.
> PABundleRefresher.isInstallerBundleAffected() does not seem to work in all
> cases
> --------------------------------------------------------------------------------
>
> Key: SLING-2567
> URL: https://issues.apache.org/jira/browse/SLING-2567
> Project: Sling
> Issue Type: Bug
> Components: Installer
> Affects Versions: Installer Core 3.3.8
> Reporter: Bertrand Delacretaz
> Priority: Minor
> Attachments: bundles-to-refresh.txt
>
>
> I'll attach a list of bundles that, in my tests, caused the installer bundle
> to be stopped although PABundleRefresher.isInstallerBundleAffected() returns
> false.
> I assume that's because the installer core bundle is indirectly affected by
> the refreshed bundles, but I haven't investigated in detail yet.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
