On Tue, Sep 22, 2015 at 8:36 AM, Julian Sedding wrote:
> ...By specifying the desired deployment state in a provisioning model file,
> the installer could make sure it has all required artifacts available (e.g.
> local folder, maven repository, etc). Once that is the case it could
> update/install
Maybe this is abit far fetched. I get the impression that we are (need to
be) moving from a "per artifact" towards a "deployment" paradigm.
Approaches pioneered by crankstart and the provisioning model may become
desirable (as an option) for the installer.
By specifying the desired deployment st
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
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.
Justin
On Mon, Sep 21, 2015 at 1:26 PM Carsten Ziegeler
wrote:
> Unfortunately, the OSGi inst
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 anything. I think the eas
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 version
On Mon, Sep 21, 2015 at 12:05 PM, Jason Bailey wrote:
> 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
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 [m
Is it possible to control the JcrInstaller behavior (which utilizes the
OsgiInstaller functionality) to indicate whether a bundle should be
considered a "new install" rather than an "update"?
e.g.
upload guava-17.0.jar to /apps/a/install/guava-17.0.jar
This creates a new bundle registered within F
