Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 33661 - [Tasks] Cannot get rid of warnings from closed project
Summary: [Tasks] Cannot get rid of warnings from closed project
Status: RESOLVED DUPLICATE of bug 33481
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.1   Edit
Hardware: PC Windows XP
: P2 major (vote)
Target Milestone: 2.1 RC2   Edit
Assignee: Chris McLaren CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-03-03 09:46 EST by Tod Creasey CLA
Modified: 2003-03-10 15:15 EST (History)
1 user (show)

See Also:

Attachments
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 Tod Creasey CLA 2003-03-03 09:46:06 EST 
20030227

If you close a project and then rebuild some of the warnings will be left. 
Deleting the project and rebuilding will not get rid of them either.

STEPS
1) Set Usage of Non-Externalized Strings to warning
2) Load org.eclipse.ui.tests
3) There are lots of NL warnings
4) Close org.eclipse.ui.tests
5) Rebuild Over 250 warnings are still there.
6) Delete it. Rebuild.
7) Warnings don't change.
Comment 1 Tod Creasey CLA 2003-03-03 10:04:47 EST 
Note that restarting Eclipse will get rid of these problems
Comment 2 Philipe Mulet CLA 2003-03-03 12:41:12 EST 
Wondering if the task lists isn't rather still showing information it should 
not (why showing markers for a closed project?).

Nick - Is this possible ?
Comment 3 Nick Edgar CLA 2003-03-03 12:47:33 EST 
There have been some other refresh problems reported against the Tasks view, 
which may be related to some recent viewer changes.  I'll investigate.
Comment 4 Nick Edgar CLA 2003-03-03 23:17:18 EST 
Cannot reproduce in I20030227.
Tod, can you demo this to me?
Comment 5 Tod Creasey CLA 2003-03-04 15:26:49 EST 
This appears to be a NullPointerException from the resourceListener. 
Reassigning as requested:

!ENTRY org.eclipse.core.resources 4 2 Mar 04, 2003 13:23:58.828
!MESSAGE Problems occurred when invoking code from plug-
in: "org.eclipse.core.resources".
!STACK 0
java.lang.NullPointerException
	at 
org.eclipse.ui.views.tasklist.TaskListContentProvider.resourceChanged
(TaskListContentProvider.java(Compiled Code))
	at 
org.eclipse.ui.views.tasklist.TaskListContentProvider.resourceChanged
(TaskListContentProvider.java(Compiled Code))
	at 
org.eclipse.ui.views.tasklist.TaskListContentProvider.resourceChanged
(TaskListContentProvider.java(Compiled Code))
	at 
org.eclipse.ui.views.tasklist.TaskListContentProvider.resourceChanged
(TaskListContentProvider.java(Compiled Code))
	at org.eclipse.core.internal.events.NotificationManager$1.run
(NotificationManager.java:137)
	at org.eclipse.core.internal.runtime.InternalPlatform.run
(InternalPlatform.java(Compiled Code))
	at org.eclipse.core.internal.events.NotificationManager.notify
(NotificationManager.java(Compiled Code))
	at org.eclipse.core.internal.events.NotificationManager.notify
(NotificationManager.java(Compiled Code))
	at 
org.eclipse.core.internal.events.NotificationManager.broadcastChanges
(NotificationManager.java:67)
	at org.eclipse.core.internal.resources.Workspace.broadcastChanges
(Workspace.java:161)
	at org.eclipse.core.internal.resources.Workspace.endOperation
(Workspace.java(Compiled Code))
	at org.eclipse.core.internal.resources.Workspace.run(Workspace.java
(Compiled Code))
	at org.eclipse.ui.actions.WorkspaceModifyOperation.run
(WorkspaceModifyOperation.java:79)
	at org.eclipse.team.internal.ccvs.ui.repo.RepositoryManager.run
(RepositoryManager.java:785)
	at org.eclipse.team.internal.ccvs.ui.actions.CVSAction$1.run
(CVSAction.java:242)
	at org.eclipse.jface.operation.ModalContext$ModalContextThread.run
(ModalContext.java:95)
Comment 6 Tod Creasey CLA 2003-03-04 15:50:55 EST 
When I copy the workbench and run it self hosted with what is currently in the 
HEAD stream I do not get this problem.
Comment 7 Nick Edgar CLA 2003-03-10 15:15:45 EST 

*** This bug has been marked as a duplicate of 33481 ***