[
https://issues.apache.org/jira/browse/SLING-2567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13437863#comment-13437863
]
Carsten Ziegeler commented on SLING-2567:
-----------------------------------------
The installer embedds a single class (for the configuration file format), but
that is not revealed in any of the manifest headers, so I don't think that this
is causing the refresh.
I asume it's more a 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
