Description Nick Edgar 2001-10-10 22:42:57 EDT

From EC post: "Export to Filesystem fails" by PG on Aug 21, 2001.

I had a group of html files in a project to export.  Some of the files
were configured to use the default text editor.  Others were configured to
use an external editor (a GUI vi clone called gvim).  The ones that were
configured to use gvim failed to export.  The ones configured to use the
default editor suceeded.  Upon changing all file to use the Workbench text
editor by default, the export of all files succeeded.

Also, the "Details" button of the error panel told me which files failed
to export, but not the reason why.

I am using "jre-win32-Eclipse-SDK-SHIPPED-0.128.zip".

NOTES:

NE (8/22/01 11:35:21 AM)
This is probably due to the workspace being out of synch with the filesystem.
Before you export, try choosing "Refresh From Local" in the Navigator's popup menu 
with the project selected.
I've filed a problem report for this, since there doesn't seem to be any reason why you 
shouldn't be able to export even if it's out of sync.
Also, as you point out, the error reporting could use some improvement.

EJP (10/3/2001 4:46:13 PM)
	Suggestion: The catch block in the exportFile (zip and etc) could create a MultiStatus instead.
	So the user would know why it failed to export.

	} catch (CoreException e) {
		MultiStatus status = new MultiStatus(
				PlatformUI.PLUGIN_ID,
				0,
				DataTransferMessages.format(
					"DataTransfer.errorExporting", //$NON-NLS-1$
					new Object[] { fullPath }),
				e);
		status.add(e.getStatus());
		errorTable.add(status);
	}
	
	The same idea could be used for the IOException as well.