Bug 160005 - Add protection about misbehaving container initializer
Summary: Add protection about misbehaving container initializer
Status: VERIFIED FIXED
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.3 M3   Edit
Assignee: Jerome Lanneluc CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-10-06 09:41 EDT by Jerome Lanneluc CLA
Modified: 2006-10-30 15:10 EST (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 Jerome Lanneluc CLA 2006-10-06 09:41:30 EDT 
I20061003

As shown in bug 159989, the PDE container is misbehaving and it is not initializing the container it should initialize. As a consequence, an infinite loop occurs beacause we keep asking the container initialize to initialize the container.
Comment 1 Jerome Lanneluc CLA 2006-10-09 06:54:16 EDT 
Changed JavaModelManager#getClsspathContainer(IPath, IJavaProject) to return a default classpath container (see ClasspathContainerInitializer#getFailureContainer(...)) if the initializer failed to initialize the container.
Added regression test ClasspathInitializerTests#testContainerInitializer14().
Released for 3.3 M3 in HEAD.
Comment 2 Olivier Thomann CLA 2006-10-30 15:10:16 EST 
Verified for 3.3 M3 using warm-up build I20061030-0800 by checking source code.