Bug 209558 - [Import/Export] FileSystemImportWizard and FileSystemExportWizard require the compatibility plug-in
Summary: [Import/Export] FileSystemImportWizard and FileSystemExportWizard require the...
Status: VERIFIED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.3.1   Edit
Hardware: PC Windows XP
: P3 minor with 1 vote (vote)
Target Milestone: 3.4   Edit
Assignee: Tod Creasey CLA
QA Contact:
URL:
Whiteboard: hasPatch
Keywords: contributed
: 191722 (view as bug list)
Depends on:
Blocks:
 
Reported: 2007-11-12 16:50 EST by Andreas Ortloff CLA
Modified: 2008-01-30 09:56 EST (History)
3 users (show)

See Also:

Attachments
Patch to fix the two wizards in question by calling WorkbenchPlugin.getDefault() instead. (4.68 KB, patch)
2007-11-16 18:21 EST, Remy Suen CLA 		no flags Details | Diff
Patch to fix ZipFileExportWizard also. (6.96 KB, patch)
2007-11-19 10:46 EST, Remy Suen CLA 		no flags Details | Diff
Show Obsolete (1) View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Andreas Ortloff CLA 2007-11-12 16:50:59 EST 
Build ID: M20070921-1145

Steps To Reproduce:
1.Create an RCP app.
2.Add an export wizard to plugin.xml, pointing to org.eclipse.ui.wizards.datatransfer.ZipFileExportWizard. Could also just invoke it from code, like in an action.
3.Attempt to run the wizard and observe the error message.


More information:
ZipFileImportWizard, ExternalProjectImportWizard, PreferencesImportWizard, and PreferencesExportWizard can be brought up fine in the same RCP app, while FileSystemImportWizard and FileSystemExportWizard issue the message. The difference is that the wizards which start up call WorkbenchPlugin.getDefault(), while the ones which don't call the deprecated method Platform.getPlugin(). I figured out that adding the org.eclipse.core.runtime.compatibility plug-in to the dependency list allows all the wizards to start up without the message. It seems like perhaps all these classes ought to be calling WorkbenchPlugin.getDefault() now.
Comment 1 Andreas Ortloff CLA 2007-11-12 16:59:32 EST 
Note that when reproducing the error one will want to edit the list of plug-ins in the run configuration to only include the required ones. If one launches with all available plung-ins, the error won't occur.
Comment 2 Remy Suen CLA 2007-11-16 18:21:09 EST 
Created attachment 83135 [details]
Patch to fix the two wizards in question by calling WorkbenchPlugin.getDefault() instead.
Comment 3 Tod Creasey CLA 2007-11-19 07:51:35 EST 
Thanks once again Remy
Comment 4 Andreas Ortloff CLA 2007-11-19 10:37:09 EST 
Yes, thanks Remy. There is another wizard which has this problem - ZipFileExportWizard.
Comment 5 Remy Suen CLA 2007-11-19 10:46:57 EST 
Created attachment 83243 [details]
Patch to fix ZipFileExportWizard also.
Comment 6 Tod Creasey CLA 2007-11-26 14:50:28 EST 
Patch released for build >20071126
Comment 7 Tod Creasey CLA 2007-12-10 13:53:13 EST 
Verified in Version: 3.4.0
Build id: I20071210-0930
Comment 8 Tod Creasey CLA 2008-01-30 09:56:17 EST 
*** Bug 191722 has been marked as a duplicate of this bug. ***