Bug 200449 - [model] Classpath variable deprecation message is not flushed from cache when variable is removed
Summary: [model] Classpath variable deprecation message is not flushed from cache when...
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.4 M2   Edit
Assignee: Frederic Fusier CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-08-18 10:16 EDT by Frederic Fusier CLA
Modified: 2007-09-18 03:21 EDT (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 Frederic Fusier CLA 2007-08-18 10:16:31 EDT 
Build I20070815-1600 but exists from initial implementation of bug 138599 in 3.3.

Since bug 138599 has been implemented, deprecation message of classpath variables are stored in a JavaModelManager cache: 'deprecatedVariables'. This cache is populated while initializing the variable classpath initializer but is never freed when the variable is removed using JavaCore#removeClasspathVariable(String) API method...
Comment 1 Frederic Fusier CLA 2007-08-18 14:01:28 EDT 
Released for 3.4M2 in HEAD stream.

The fix for this bug is available in patch attached to bug 186113.
Comment 2 Eric Jodet CLA 2007-09-18 01:10:24 EDT 
(In reply to comment #1)
Verified for 3.4 M2 using build I20070917-0010.