| PluginModelManager.initializeTable() problem in self-hosted application [message #336121] |
Fri, 22 May 2009 15:17 |
 Mikhail Kadan
Messages: 61
Registered: July 2009 |
Member |
|
|
Hello.
I am using Eclipse 3.4.2. Then I:
1) created new plug-in ("MyPlugin") in workspace,
2) added code to call PluginRegistry.getActiveModels() to it
3 created Eclipse application launcher which includes all workspace and
target plug-ins
4) created explicit config.ini for this launcher, which starts
"org.eclipse.update.configurator" (because I'm using old update mechanism)
now when I launch self-hosted application using created launcher and call
PluginRegistry.getActiveModels() it doesn't return "MyPlugin" among other
plugins
What I have discovered so far:
1) if I remove my "config.ini" (and thus enable p2 update mechanism),
"MyPlugin" is returned properly
2) then I debugged PluginRegistry.getActiveModels() and discovered that it
calls PluginModelManager.initializeTable() which in turn read platform
configuration from:
*) if p2 is enabled:
file:/C:/Work/workspaces/xdoc/.metadata/.plugins/org.eclipse .pde.core/runtime-New_launcher/org.eclipse.equinox.simplecon figurator\bundles.info
*) if old updater is enabled:
C:\Work\eclipse\configuration\org.eclipse.update\platform.xm l
As I can see from this paths, p2 updater reads configuration file related
to launcher, so it will gather all parent's workspace plug-ins as well;
and old updater reads configuration file related parent eclipse instance,
which of course it don't know about plug-ins in parent's workspace; and I
think this is the root of problem
Is there any possibility to make old updater behave properly in
self-hosted applications?
Thanks.
|
|
|
Powered by
FUDForum. Page generated in 0.02902 seconds
] 
Search
Help
Register
Login
Home
