|Re: [equinox-dev] Choosing which version of a bundle to start after the workbench starts|
Thanks, Neil.Â I'll have to try this to make sure, but starting the bundle that I want doesn't prevent the bundle I don't want from starting.Â Eg- if I want version 1.8.6 and I call start(START_TRANSIENT) on it, I think the 2.0.0 version will still be started.I'll try this to make sure, though.
On Thu, Apr 11, 2013 at 10:22 AM, Neil Bartlett <njbartlett@xxxxxxxxx> wrote:
Why not start the bundle transiently (ie. Bundle.START_TRANSIENT) from another ordinary bundle? Since the target bundle's start-state is not persisted, you will be able to decide each time which bundle to start.Neil
On Thu, Apr 11, 2013 at 6:18 PM, Andrew Eisenberg <andrew@xxxxxxxxxxxx> wrote:
I have multiple versions of a bundle installed in my Eclipse installation.Â After the workbench starts up, I need to make a decision as to which version of the bundle should be started based on a system property that the user passes in from the command line.Â Currently, I am doing this through a framework adapter that adds a BundleInfo to disable/enable appropriate versions of the bundle as the workbench starts up, but this is brittle and has limitations.
This bundle is not a singleton and all downstream bundles depend on a version range that includes all possible candidates of this bundle.
So my question is: is there any way to control which version of the plugin starts without using BundleInfos?Â I can provide more details if you need.
thanks for your help,
equinox-dev mailing list