Bug 254439 - [GlobalActions] Refresh action throws NPE for missing EFS implementation
Summary: [GlobalActions] Refresh action throws NPE for missing EFS implementation
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.5   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-11-06 08:11 EST by Benjamin Muskalla CLA
Modified: 2019-09-06 16:11 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Benjamin Muskalla CLA 2008-11-06 08:11:45 EST
N20081025-2000

* Use a workspace with a project that uses a non-default EFS implementation (rse in my case)
* close project
* uninstall efs provider
* restart eclipse
* refresh all projects

Log contains a warning "No file system is defined for scheme: rse" which is ok but the refresh action throws the following NPE.

-- Error Details --
Date: Thu Nov 06 14:06:50 CET 2008
Message: An internal error occurred during: "Refresh".
Severity: Error
Plugin: org.eclipse.core.jobs
Session Data:
eclipse.buildId=N20081025-2000
java.version=1.6.0_0
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
Command-line arguments:  -os linux -ws gtk -arch x86


Exception Stack Trace:
java.lang.NullPointerException
	at org.eclipse.ui.actions.RefreshAction.checkLocationDeleted(RefreshAction.java:114)
	at org.eclipse.ui.actions.RefreshAction.refreshResource(RefreshAction.java:285)
	at org.eclipse.ui.actions.RefreshAction$2.execute(RefreshAction.java:245)
	at org.eclipse.ui.actions.WorkspaceModifyOperation$1.run(WorkspaceModifyOperation.java:106)
	at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800)
	at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:118)
	at org.eclipse.jdt.ui.actions.RefreshAction$WrappedWorkbenchRefreshAction.run(RefreshAction.java:112)
	at org.eclipse.jdt.ui.actions.RefreshAction.performRefresh(RefreshAction.java:190)
	at org.eclipse.jdt.ui.actions.RefreshAction.access$0(RefreshAction.java:185)
	at org.eclipse.jdt.ui.actions.RefreshAction$1.run(RefreshAction.java:179)
	at org.eclipse.jdt.internal.core.BatchOperation.executeOperation(BatchOperation.java:39)
	at org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:721)
	at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800)
	at org.eclipse.jdt.core.JavaCore.run(JavaCore.java:4635)
	at org.eclipse.jdt.internal.ui.actions.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:92)
	at org.eclipse.jdt.internal.ui.actions.WorkbenchRunnableAdapter$1.run(WorkbenchRunnableAdapter.java:107)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Comment 1 Eclipse Webmaster CLA 2019-09-06 16:11:22 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.