You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Konrad Windszus (Jira)" <ji...@apache.org> on 2020/06/04 16:03:00 UTC
[jira] [Assigned] (SLING-9502) Document pitfalls of the
installer-provider-installhook
[ https://issues.apache.org/jira/browse/SLING-9502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konrad Windszus reassigned SLING-9502:
--------------------------------------
Assignee: Konrad Windszus
> Document pitfalls of the installer-provider-installhook
> -------------------------------------------------------
>
> Key: SLING-9502
> URL: https://issues.apache.org/jira/browse/SLING-9502
> Project: Sling
> Issue Type: Improvement
> Components: Installer
> Affects Versions: Installer Vault Package Install Hook 1.1.0
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Priority: Major
>
> The page at [https://sling.apache.org/documentation/bundles/installer-provider-installhook.html] should outline that a synchronous deployment of bundles comes also with some drawbacks which is why https://issues.apache.org/jira/browse/SLING-3747 has been added in the first place.
> For example the composum package manager ([https://github.com/ist-dresden/composum/blob/develop/sling/core/pckgmgr/src/main/java/com/composum/sling/core/pckgmgr/PackageJobExecutor.java#L226]) depends on the Sling Dynamic Class Loader which might restart after a bundle deployment. Further information about that in [https://lists.apache.org/thread.html/57d56e31da3c1cb743cf524e0c85e46959f3af9ed946f2c4a41d33c0@%3Cdev.sling.apache.org%3E].
> Those pitfalls should be documented at [https://sling.apache.org/documentation/bundles/installer-provider-installhook.html] to make clear that this hook is not the silver bullet.
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)