Re: Control JcrInstaller (OsgiInstaller) Behavior of Bundle Updating vs Installing

Am 22.09.15 um 01:24 schrieb Justin Edelson: > IMHO, coming up with general rules is going to be close to impossible. > Instead, we should make this configuration explicit, I.e. Have a > configuration on the installer which declares the action per BSN. > Well, right now we have general rules and

RE: Control JcrInstaller (OsgiInstaller) Behavior of Bundle Updating vs Installing

I'm a bit confused by the use case. Breakage should only occur if the bundle is exporting an API that is versioned, and you have a bundle that is explicitly set to not accept the new package version. Or is the breakage somewhere else? -Jason -Original Message- From: Steven Walters

Re: Control JcrInstaller (OsgiInstaller) Behavior of Bundle Updating vs Installing

Unfortunately, the OSGi installer does not support this use case, and the same goes with the web console from Apache Felix. Actually, this feature has been requested several times, but so far we never did anything. I think the easiest way would be to make the distinction based on the major

Re: Control JcrInstaller (OsgiInstaller) Behavior of Bundle Updating vs Installing

On Mon, Sep 21, 2015 at 1:26 PM, Carsten Ziegeler wrote: > Unfortunately, the OSGi installer does not support this use case, and > the same goes with the web console from Apache Felix. > > Actually, this feature has been requested several times, but so far we > never did