Pax Runner: persisting cache state / auto update bundles

[Pieter]

Hi,

I just decided the Felix Preference service could be useful for me to
store application parameters and have them survive system restart.
Since it stores it data in the Felix cache directory I figured I
needed to set org.ops4j.pax.runner.platform.usePersistedState to true
in order to keep the data.

Now when I update a bundle's version number in Pax Runner's provision
profile I end up with two versions of the bundle being installed. The
new version is installed as expected, but the old version is still
there too. I can uninstall it via the shell, but that's not a workable
solution to keep doing.

So my question is; how do I handle bundle upgrades when not dropping
the cache directory on restart?

Cheers,
Pieter

[Niclas Hedhman]

I think you can create a symlink that Felix uses, which links to the
version you want to use. A bit of scripting and/or a custom URL
handler is probably the solution. But I have been away for a while, so
there might be better ones...

> --
> ------------------
> OPS4J - http://www.ops4j.org - op...@googlegroups.com

--
Niclas Hedhman, Software Developer
http://www.qi4j.org - New Energy for Java

I  live here; http://tinyurl.com/2qq9er
I  work here; http://tinyurl.com/2ymelc
I relax here; http://tinyurl.com/2cgsug