Bug 91685 - PDE container entries different on startup than on shutdown
Summary: PDE container entries different on startup than on shutdown
Status: RESOLVED FIXED
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.1 M7   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-04-17 13:55 EDT by Jerome Lanneluc CLA
Modified: 2005-04-17 15:42 EDT (History)
0 users

See Also:

Attachments
Example of missbehaving container trace (8.90 KB, text/plain)
2005-04-17 13:59 EDT, Jerome Lanneluc CLA 		no flags Details
View All 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 2005-04-17 13:55:57 EDT 
I20040514 + org.eclipse.jdt.core from HEAD

1. Take latest org.eclipse.jdt.core (note you can trust HEAD as always being as
good as an integration build)
2. Turn on classpath resolution tracing:
org.eclipse.jdt.core/debug/cpresolution=true
3. Startup a full source 3.0 workspace
Observe: you get 'missbehaving container' traces in the console indicating that
the classpath entries of the org.eclipse.pde.core.requiredPlugins container are
different on startup than they were on last shutdown.
Comment 1 Jerome Lanneluc CLA 2005-04-17 13:59:51 EDT 
Created attachment 19979 [details]
Example of missbehaving container trace

In this example, the order of the swt and osgi plugins is not consistent.
Comment 2 Wassim Melhem CLA 2005-04-17 15:38:31 EDT 
good catch.
This is a new bug that was introduced into the I-20050413 build (when the new 
state-based classpath computation was released) and has now been corrected.
So I doubt it was the cause of the long-standing full build problem.  However, 
it certainly didn't help.
Comment 3 Wassim Melhem CLA 2005-04-17 15:42:20 EDT 
In this case, the last two entries which are in the wrong order shouldn't even 
be there.  

the project would get osgi for free via the first entry (core.runtime)
and would also get swt for free via the org.eclipse.ui project entry.

The fact that those two entries redundantly appeared at the end is the real 
bug.