Project: Eclipse_Platform_UI
Bug 55065 [RCP] early startup mechanism needs to use reflect if compatibility is not available
Reported: 2004-03-16 22:18:01 | Status: resolved fixed

The new early activation mechansim allows a class to be specified in the extension. If the class is not present then the supplying plugin's Plugin class is used. In Eclipse 3.0 we cannot access random plugin objects unless the runtime compatibility code is present. To support cases where it is not present, the current implementation that uses the Plugin object should be changed to use reflection.

Files changed in fix:
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/Workbench.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/dialogs/StartupPreferencePage.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/registry/RegistryManager.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/registry/ViewRegistry.java