[
https://issues.apache.org/jira/browse/SLING-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12764675#action_12764675
]
Bertrand Delacretaz commented on SLING-1147:
--------------------------------------------
I haven't been able to reproduce this behavior, here's my scenario:
1. Start sling launchpad/app, add runmode, osgi.installer and jcrinstall
bundles from revision 824323
2. Install a test bundle version 1.0.0 via jcrinstall -> OK
3. Install V1.0.2-SNAPSHOT of same bundle via webconsole -> OK (as long as
nothing triggers SLING-1106)
4. Restart launchpad/app -> bundle downgraded to 1.0.0, caused by SLING-1106
Carsten (as you reported this problem in SLING-1106) , do you have a different
scenario that demonstrates your problem?
> Installing SNAPSHOT of bundle installed via jcrinstall causes both bundles to
> be active
> ---------------------------------------------------------------------------------------
>
> Key: SLING-1147
> URL: https://issues.apache.org/jira/browse/SLING-1147
> Project: Sling
> Issue Type: Bug
> Components: Installer
> Reporter: Bertrand Delacretaz
> Assignee: Bertrand Delacretaz
> Priority: Minor
>
> (from SLING-1106)
> 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.
