It is valid to wire to uninstalled bundles since they still exist and it
might even make more sense to do so, since other bundles are obviously
still wired to the uninstalled bundle otherwise it wouldn't still exist.
Wiring to a different bundle will definitely partition the class space
since s
I understand that, but in my case, I am sure that the 3 bundles that I
have uninstalled were not used by any other bundle.
And also my use case is simply reinstalling the same bundles after
having used them and uninstalled them.
I tried already to call PackageAdmin.refreshPackages() as mentioned i
On 06/11/2011 02:41 PM, Etienne Vrignaud wrote:
I understand that, but in my case, I am sure that the 3 bundles that I
have uninstalled were not used by any other bundle.
If a bundle is uninstalled and no one is using it then it will go away,
it only sticks around if someone is using it. You
Justin, again thanks for your inputs.
Extending your example of Project A, B and C, but I'm not keen on
knowing the transitive dependencies of B, which might be using 2.0
version of C. A also has a dependency on commons-lang 2.5. I've
constructed the following plugin bundle entry.
Peter:
makes perfect sense; thank you.
Andrei
Original Message
Subject: Re: ConfigurationAdmin & SCR component self-update
From: Peter Kriens
To: users@felix.apache.org
Date: Wed 08 Jun 2011 07:51:25 AM CDT
> The basic idea is that when the user updates the window position
5 matches
Mail list logo
