[
https://issues.apache.org/jira/browse/SLING-2217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-2217.
-------------------------------------
Resolution: Fixed
There were some problems when the name of the bundle did not change, in both
situations upgrading and downgrading.
I've fixed this in revision 1183262
> Need a good way to downgrade a bundle
> -------------------------------------
>
> Key: SLING-2217
> URL: https://issues.apache.org/jira/browse/SLING-2217
> Project: Sling
> Issue Type: Improvement
> Components: Installer
> Affects Versions: Installer Core 3.2.0
> Reporter: Andrew Khoury
> Assignee: Carsten Ziegeler
> Priority: Minor
> Fix For: Installer Core 3.2.4
>
>
> The JCR install module should allow for downgrading to an older version of a
> bundle if the bundle jar is replaced. This is relevant when you do a release
> of a bundle in a QA or Staging environment and later decide that the release
> should be rolled back to the old version. It might make sense to just to
> simplify things by reinstalling the bundle to the osgi container whenever the
> jar file is replaced.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
