Not sure if you are dealing with bundles that have the lazy activation policy. If so you may be running into a hack in Equinox to support p2. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=177641
As Neil suggests you may have to persistently stop all the other versions
of the bundle that you want to not be started.
Tom
From: Neil Bartlett <njbartl...@gmail.com>
To: and...@eisenberg.as,
Cc: Equinox development mailing list <equinox-dev@eclipse.org>
Date: 04/11/2013 12:51 PM
Subject: Re: [equinox-dev] Choosing which version of a bundle to start
after the workbench starts
Sent by: equinox-dev-boun...@eclipse.org
Bundle version 2.0.0 will only be started if somebody explicitly starts it,
or if it has already been put into the persistently-started state, or if it
is listed in config.ini with @start.
If you're unsure of the current persisted state of all the bundles, your
"starter" bundle should probably explicitly stop ALL versions before
transiently starting the selected version.
Neil
On Thu, Apr 11, 2013 at 6:42 PM, Andrew Eisenberg <and...@eisenberg.as>
wrote:
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 <njbartl...@gmail.com>
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 <and...@eisenberg.as>
wrote:
Hi all,
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,
Andrew
_______________________________________________
equinox-dev mailing list
equinox-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/equinox-dev
_______________________________________________
equinox-dev mailing list
equinox-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/equinox-dev
<<inline: graycol.gif>>
_______________________________________________ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
