That appears to be exactly our issue. -----Original Message----- From: Robert Munteanu [mailto:[email protected]] Sent: Wednesday, November 04, 2015 8:43 AM To: [email protected] Subject: Re: Upgrading an installation
On Wed, Nov 4, 2015 at 2:15 PM, Roll, Kevin <[email protected]> wrote: > Hi, Bertrand. I've been trying to think of how I could provide an example. > Our basic scenario is that we have an installed Sling, we overwrite the > standalone jar with one that contains a *new* bundle, and when we start the > bundle is not there. Adding the 'upgrade' flag seems to have solved the issue. Without knowing the details of your launcher, the problem sounds a little bit like https://issues.apache.org/jira/browse/SLING-3307 Of course, depending on your specific scenario, it might be unrelated. Robert > > -----Original Message----- > From: Bertrand Delacretaz [mailto:[email protected]] > Sent: Monday, November 02, 2015 10:05 AM > To: users > Subject: Re: Upgrading an installation > > Hi, > > On Fri, Oct 30, 2015 at 8:16 PM, Roll, Kevin <[email protected]> wrote: >> ...The problem comes when we upgrade to a new version and provide a >> newer standalone launcher.... > > Could you provide a minimal example (source code) that demonstrates the > problem? > > I'm not saying it does not happen, just want to make sure we test it > with the exact same setup as you do. > > -Bertrand
