| Equinox OSGi Framework Launcher [message #1101555] |
Wed, 04 September 2013 16:07 |
 Peter Nehrer
Messages: 241
Registered: July 2009 |
Senior Member |
|
|
Hi,
I have an Equinox OSGi Framework launch configuration based on
explicitly selected features -- the features determine the full closure
of what bundles (including fragments) I want to launch.
However, this ends up launching all fragments that happen to be
available in the workspace and target platform whose hosts I launch
*even though* they're not included in the selected features.
This is annoying -- it effectively prevents me from using this type of
launch configuration and I'm stuck with having to maintain a launch file
with explicitly selected bundles that reflect the features I want to launch.
After digging through some code I found a block that adds "required
bundles" after collecting everything included in the features:
org.eclipse.pde.internal.launching.launcher.BundleLauncherHelper.getMergedBundleMap(ILaunchConfiguration,
boolean):
....
if
(configuration.getAttribute(IPDELauncherConstants.USE_CUSTOM_FEATURES,
false)) {
// Get the default location settings
....
// Get all available features
....
// Get the selected features and their plugin resolution
....
// Get all required plugins
// exclude "org.eclipse.ui.workbench.compatibility" - it is only
needed for pre-3.0 bundles
....
My question is, why do we "Get all required plugins" after we've already
collected all bundles that are selected by the features?
I'd like to understand the intent behind this in this use-case (where
the user supposedly wants to select specific bundles to include).
Thanks!
|
|
|
Powered by
FUDForum. Page generated in 0.03420 seconds
] 
Search
Help
Register
Login
Home
