[
https://issues.apache.org/jira/browse/SLING-6528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus resolved SLING-6528.
------------------------------------
Resolution: Fixed
Fixed in
https://github.com/apache/sling-org-apache-sling-installer-factory-packages/commit/9cc17c3c7f695bf597b316b90b706226ab047bb4
> Installation of a package through the package manager should trigger a new
> cycle in the OSGi Installer
> ------------------------------------------------------------------------------------------------------
>
> Key: SLING-6528
> URL: https://issues.apache.org/jira/browse/SLING-6528
> Project: Sling
> Issue Type: Bug
> Components: Installer
> Affects Versions: Installer Packages Factory 1.0.0
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Priority: Major
> Fix For: Installer Packages Factory 1.0.0
>
>
> Whenever a content-package is lacking some dependencies the installation is
> deferred in
> https://github.com/apache/sling/blob/trunk/installer/factories/packages/src/main/java/org/apache/sling/installer/factory/packages/impl/PackageTransformer.java#L234.
> If the dependency is now installed via the package manager directly (instead
> of using the OSGi Installer), the dependent package is not being installed
> till some other event causes the next OSGi Installer cycle, because the OSGi
> Installer simply won't detect that "external" installation.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
