Hi, Robert. We are using Sling/Jackrabbit as a back-end data store for an application which is distributed across a wide number of client sites. We are mainly using Jackrabbit to store images, plus some servlets and tasks in Sling as supporting pieces. Building a standalone jar seemed like the easiest way to distribute this system - we just install one jar, run it, and all of Sling unpacks and becomes available, along with our additional code. The alternative would be to attempt installation of various bundles, which would require Sling to be up and running. If there is another way to do this I am certainly open to suggestions.
-----Original Message----- From: Robert Munteanu [mailto:romb...@apache.org] Sent: Friday, October 30, 2015 5:16 PM To: users@sling.apache.org Subject: Re: Upgrading an installation Hi Kevin, I have a suggestion and a question :-) On Fri, Oct 30, 2015 at 9:16 PM, Roll, Kevin <kevin-r...@idexx.com> wrote: > We are having an issue that I don't see addressed in the pages on the Sling > Launcher. We build our own launcher which takes the standard bundles plus a > few of our own and run it in standalone mode. Why do you have your own launcher? Is there something not provided out-of-the-box by Sling? > The problem comes when we upgrade to a new version and provide a newer > standalone launcher. It appears that the existing bundles are not overwritten > with the newer versions. Is this expected behavior, and is there a safe, > approved way to force the bundles to be upgraded? The server will be shut > down when this takes place. Thanks! Have you tried setting -Dorg.apache.sling.launchpad.startupmode=update on the command line ? Thanks, Robert
