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 (JIRA)" <ji...@apache.org> on 2009/01/27 15:50:59 UTC

[jira] Updated: (SLING-842) Update installed bundles with updated and new bundles from launchpad

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

Carsten Ziegeler updated SLING-842:
-----------------------------------

    Component/s: Launchpad

> Update installed bundles with updated and new bundles from launchpad
> --------------------------------------------------------------------
>
>                 Key: SLING-842
>                 URL: https://issues.apache.org/jira/browse/SLING-842
>             Project: Sling
>          Issue Type: Improvement
>          Components: Launchpad
>    Affects Versions: Launchpad Base 2.0.2
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For: Launchpad Base 2.0.4
>
>
> The BootstrapInstaller should be enhanced to be able to update bundles which are already installed in the framework. Currently, the BootstrapInstaller creates a marker file, which causes the BootstrapInstaller to not do anything in future invocations.
> This may be enhanced such that the marker file contains the timestamp of the launcher JAR file. If a new launcher JAR file is used the BootstrapInstaller should read the enclosed list of bundles and decide for each bundle file whether to install it, update an existing bundle or ignore it. This would also allow for an simple update path for existing Sling installations.

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