[
https://issues.apache.org/jira/browse/SLING-2217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13126465#comment-13126465
]
Carsten Ziegeler commented on SLING-2217:
-----------------------------------------
Confirmed that this is bug. It seems that the installer does not detect that
this is a replacement of the artifact, it ends up with the artifact twice in
the list and therefore the higher version wins
A workaround is to use different names by adding the version to the name. If
you first add the lower version and then remove the higher version from the
repository, the installer detects this as a downgrade.
However, I'll try to fix the problem
> 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: JCR Installer 3.1.0
> Reporter: Andrew Khoury
> Assignee: Carsten Ziegeler
> Priority: Minor
>
> 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
