When making this update document we should also include roll back instructions/procedure (2.2.5 -> 2.2.2).
Cheers, Jamie On Thu, Feb 16, 2012 at 6:35 AM, Jean-Baptiste Onofré <[email protected]> wrote: > Hi Xilai, > > Removing the data folder, and upgrading/merging etc, system, lib should do > the stuff. > > I raised a Jira to document an update process. > > More over, thanks to profiles, it should be easy to apply a profile a new > Karaf instance (whatever the version is). > > Regards > JB > > > On 02/16/2012 08:39 AM, XiLai Dai wrote: >> >> Hello, >> >> Just a question from user/production point of view, what is a better way >> to get karaf container upgrade to a new version with all of the >> features/bundles/config files existing in the old version karaf >> container? E.g. from karaf 2.2.2 -> karaf 2.2.5. it’s really boring to >> redeploy these user artifacts again manually L, are there some approach >> or tools/scripts or something else can make this process more >> “automatically”? or is it possible to have a script to upgrade existing >> karaf container which replace the system artifacts which within the >> lib/, system/ directory to the new version artifacts? Thanks! >> >> Regard >> >> Xilai >> > > -- > Jean-Baptiste Onofré > [email protected] > http://blog.nanthrax.net > Talend - http://www.talend.com
