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 2017/02/20 10:28:44 UTC

[jira] [Created] (SLING-6528) Installation of a package through the package manager should trigger a new cycle in the OSGi Installer

Konrad Windszus created SLING-6528:
--------------------------------------

             Summary: 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
             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 dependent package 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
(v6.3.15#6346)