You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Andrew Khoury (Commented) (JIRA)" <ji...@apache.org> on 2012/01/31 12:12:12 UTC

[jira] [Commented] (SLING-2217) Need a good way to downgrade a bundle

    [ https://issues.apache.org/jira/browse/SLING-2217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13196838#comment-13196838 ] 

Andrew Khoury commented on SLING-2217:
--------------------------------------



I will be out of the office until Monday.  Please contact my manager Eren Aydin eaydin@adobe.com in my absense.

Thanks,

Andrew


                
> 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.3.0
>
>
> 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