[jira] [Resolved] (SLING-2567) PABundleRefresher.isInstallerBundleAffected() does not seem to work in all cases

["Bertrand Delacretaz (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SLING-2567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bertrand Delacretaz resolved SLING-2567.
----------------------------------------

    Resolution: Fixed
      Assignee: Bertrand Delacretaz

I have reimplemented in revision 1375615 based on Felix's suggestion, thanks for that!

My complex upgrade tests that previously failed now pass (the problem was probably the missed dynamic import package).

I've left the RefreshDependenciesUtil class separate, it is reusable in this way if needed, and passes Booch's "a class should do one thing and one thing well" test. Feel free to refactor if you want.
                
> 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: 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