[jira] Updated: (SLING-1106) JCR Install prevents update of bundle through other channels like the web console

["Carsten Ziegeler (JIRA)" <ji...@apache.org>]

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

Carsten Ziegeler updated SLING-1106:
------------------------------------

    Priority: Blocker  (was: Major)
     Summary: JCR Install prevents update of bundle through other channels like the web console  (was: Updating bundle through web console results in bundle installed twice after restart)

Another scenario: when you update a bundle which has been installed by jcr install through another channel like the web console, the bundle 
gets immediately replaced by the version from jcr install. Example
JCR Install install Bundle A Version 1
Web console updates Bundle A to Verson 2
JCR Install "updates" Bundle A to Version 1

> JCR Install prevents update of bundle through other channels like the web console
> ---------------------------------------------------------------------------------
>
>                 Key: SLING-1106
>                 URL: https://issues.apache.org/jira/browse/SLING-1106
>             Project: Sling
>          Issue Type: Bug
>          Components: Installer
>            Reporter: Carsten Ziegeler
>            Priority: Blocker
>
> I have a bundle with version 2.0.5-tlp-SOMETHING in the repo (/libs/sling/install)
> Now I want to update this bundle to a snapshot version using the web console
> After a restart, both versions are active - the one updated through the web console and the one from the libs folder in the repository.

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