[
https://issues.apache.org/jira/browse/SLING-1106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz updated SLING-1106:
---------------------------------------
Description:
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 downgrades Bundle A to Version 1
(issue mentioned two distinct problems, moved first one to SLING-1147)
was:
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.
Priority: Minor (was: Blocker)
Summary: jcrinstall downgrades bundle installed via web console (was:
JCR Install prevents update of bundle through other channels like the web
console)
> jcrinstall downgrades bundle installed via 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: Minor
> Fix For: JCR Installer 3.0.2
>
>
> 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 downgrades Bundle A to Version 1
> (issue mentioned two distinct problems, moved first one to SLING-1147)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.