Bug 321867 - classpath container order mixup
Summary: classpath container order mixup
Status: VERIFIED WORKSFORME
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.6   Edit
Hardware: Macintosh Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: 3.7 M5   Edit
Assignee: Jay Arthanareeswaran CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2010-08-05 09:35 EDT by Jeff McAffer CLA
Modified: 2011-01-25 04:30 EST (History)
4 users (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 Jeff McAffer CLA 2010-08-05 09:35:11 EDT 
For some obscure reasons I have  project that needs to have the PDE classpath container before the JRE classpath container.  Using the project properties pages Order tab this configuration was set up and the projects compile fine.  The projects were then checked into SCM and subsequently checked out by another developer into a different workspace/machine.  

Problem is, the classpath container order is not respected in the new workspace.  While the text of the .classpath file looks good and the properties page looks good, the actual compilation considers the JRE classpath container first. Deleting the JRE container and re-adding it fixes the problem.

Note that the particular topic here is access restrictions.  The particular bundle at hand has a copy of some JRE classes and is exporting them for others to see.  Normally the JRE classpath container would hide these (they are com.sun....).  So when the problem happens there are access restriction errors on all references to com.sun... code.

This may be a JDT issue...
Comment 1 Darin Wright CLA 2010-08-05 10:22:06 EDT 
Moving to JDT.
Comment 2 Srikanth Sankaran CLA 2010-08-05 22:10:25 EDT 
Jay, please see what needs to be done, Thanks.
Comment 3 Jay Arthanareeswaran CLA 2010-08-06 02:56:50 EDT 
Jeff, 
Would it be possible to attach the 'other' classpath container you used? I
tried making a jar our ot some of the restricted classes from com.sun package,
however not able to reproduce the problem. Thanks.
Comment 4 Jeff McAffer CLA 2010-12-15 08:40:27 EST 
nope.  That is long gone. I;ll look to see if I can recreate but it will be a few days
Comment 5 Jay Arthanareeswaran CLA 2011-01-19 08:44:53 EST 
I haven't heard of this problem again. Hence, closing the bug. 
Jeff, please feel free to reopen if you come across this again.
Comment 6 Satyam Kandula CLA 2011-01-25 04:30:29 EST 
Verified for 3.7M5