Bug 136382 - [classpath] Discard container if not referenced on classpath
Summary: [classpath] Discard container if not referenced on classpath
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 XP
: P3 normal (vote)
Target Milestone: 3.4 M1   Edit
Assignee: Jerome Lanneluc CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-04-12 13:07 EDT by Jerome Lanneluc CLA
Modified: 2007-08-03 11:14 EDT (History)
1 user (show)

See Also:


Attachments
Regression test (2.01 KB, patch)
2006-04-12 13:27 EDT, Jerome Lanneluc CLA
no flags Details | Diff
Updated regression test (2.01 KB, patch)
2007-06-20 07:19 EDT, Jerome Lanneluc CLA
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Jerome Lanneluc CLA 2006-04-12 13:07:12 EDT
I20060412

If a container is not referenced on the classpath, we might want to remove it from  the cache. This would have the characteristic that the initializer would be called again if the container is referenced again later on (see bug 120596 comment 2 for a test case).

This would also avoid leaking containers during a session (even if this leak is very rare).

However some clients may rely on the fact that a container initializer is called only once per session for a given container path. So this change will have to wait post 3.2.
Comment 1 Jerome Lanneluc CLA 2006-04-12 13:27:47 EDT
Created attachment 38425 [details]
Regression test
Comment 2 Olivier Thomann CLA 2006-10-10 17:02:28 EDT
Classpath container issue.
Comment 3 Jerome Lanneluc CLA 2007-06-20 07:19:21 EDT
Created attachment 71859 [details]
Updated regression test
Comment 4 Jerome Lanneluc CLA 2007-06-27 09:49:55 EDT

*** This bug has been marked as a duplicate of bug 139446 ***
Comment 5 Frederic Fusier CLA 2007-08-03 11:14:27 EDT
Verified (running test) for 3.4M1 using build I20070802-0800.