Bug 94740 - Classpath container not removed from JavaModelManager
Summary: Classpath container not removed from JavaModelManager
Status: VERIFIED DUPLICATE of bug 139446
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows 2000
: P3 major (vote)
Target Milestone: 3.4 M1   Edit
Assignee: Jerome Lanneluc CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-05-11 11:06 EDT by Sébastien Gandon CLA
Modified: 2007-08-03 10:42 EDT (History)
0 users

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 Sébastien Gandon CLA 2005-05-11 11:06:47 EDT 
Hello,

When you remove a container using the Action : Build Path -> remove from Build
Path it is not removed from the container cache in 
org.eclipse.jdt.internal.core.JavaModelManger.containers.get(myProject) hash list.
This is a bug to me because when creating a new container using the same path in
the same project, it uses the cached container which to me should have been
destroyed.

Sebastien.
Comment 1 Olivier Thomann CLA 2005-05-11 12:01:43 EDT 
Update title
Comment 2 Jerome Lanneluc CLA 2005-06-10 04:58:43 EDT 
Not sure if we want to do JavaCore.setClasspathContainer(containerPath, new
IJavaProject[] {project}, new IClasspathContainer[] {null}, monitor) in the
SetClasspathOperation, or if we want to let the UI do it.

This would be a change in behavior (which is not specified) and might break
existing clients.

Will consider post 3.1
Comment 3 Jerome Lanneluc CLA 2007-07-03 12:48:05 EDT 
Same problem as bug 139446.
Comment 4 Jerome Lanneluc CLA 2007-07-03 12:48:31 EDT 

*** This bug has been marked as a duplicate of bug 139446 ***
Comment 5 Frederic Fusier CLA 2007-08-03 10:42:58 EDT 
Verified for 3.4M1 using build I20070802-0800.