You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2012/08/28 10:00:08 UTC
[jira] [Reopened] (SLING-2567)
PABundleRefresher.isInstallerBundleAffected() does not seem to work in all
cases
[ https://issues.apache.org/jira/browse/SLING-2567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler reopened SLING-2567:
-------------------------------------
Assignee: Carsten Ziegeler (was: Bertrand Delacretaz)
I just ran into a test case where this check is not working, therefore reopening
> 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
> Assignee: Carsten Ziegeler
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira