You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2007/12/18 11:26:43 UTC

[jira] Closed: (SLING-138) Initial Bundle installation

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

Felix Meschberger closed SLING-138.
-----------------------------------

    Resolution: Fixed

Implemented bootstrap bundle installation in Rev. 605168

> Initial Bundle installation
> ---------------------------
>
>                 Key: SLING-138
>                 URL: https://issues.apache.org/jira/browse/SLING-138
>             Project: Sling
>          Issue Type: Improvement
>          Components: Launcher
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For: 2.0.0
>
>
> The Felix framework was recently [1] modified such that the initial installation and automatic startup of bundles is not controlled by the framework any more but by the framework launcher. For Apache Felix this is the Main project. In Sling we now have to adapt the Sling Application Launcher to also take care of this automatic installation.
> This in fact is a good thing as we now have more control over this installation process. In particular we can solve a long standing issue where startup of a moved "sling context" logged a lot of errors because the automatically installed bundles had new location URLs.
> [1] https://issues.apache.org/jira/browse/FELIX-393

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.