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 (Resolved) (JIRA)" <ji...@apache.org> on 2011/11/14 14:28:51 UTC
[jira] [Resolved] (SLING-2283) Host bundle for a fragment should
not be refreshed when a complete package refresh is performed
[ https://issues.apache.org/jira/browse/SLING-2283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler resolved SLING-2283.
-------------------------------------
Resolution: Fixed
> Host bundle for a fragment should not be refreshed when a complete package refresh is performed
> -----------------------------------------------------------------------------------------------
>
> Key: SLING-2283
> URL: https://issues.apache.org/jira/browse/SLING-2283
> Project: Sling
> Issue Type: Bug
> Components: Installer
> Affects Versions: Installer Core 3.2.0, Installer Core 3.2.2
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Installer Core 3.2.4
>
>
> The installer does a package refresh for all bundles after a completed operation. This task also checks if all bundles, that were started before are started afterwards. With SLING-2043 this includes fragments, and causes a refresh of the host bundle for each fragment, regardless of the actual state.
> In revision 1201694 I completely disabled the restart check for fragments as it doesn't make that much sense and causes problems anyway.
> I'm really wondering if we need the whole logic at all
--
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