Bug 47416 - Random failures locating methods in JDK
Summary: Random failures locating methods in JDK
Status: RESOLVED WORKSFORME
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.0 M7   Edit
Assignee: Kent Johnson CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-11-25 08:44 EST by Jonathan Gossage CLA
Modified: 2004-01-29 06:50 EST (History)
1 user (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 Jonathan Gossage CLA 2003-11-25 08:44:16 EST 
I am running the M5 release under the Sun JDK 1.4.2-02. While most of the 
projects in my workspace run under 1.4.2, I have one project that runs under 
1.3.1. This particular project must run under both J2SE and J2ME so I use the 
following compiler options.

   Compiler compliance 1.3
   Generated .class file compatibility 1.1
   Source compatibility 1.3
   Report assert as identifier Error

In addition I replaced the 1.4.2 JRE in the Libraries Tab of the Java Build 
Path in the project properties with the 1.3.1 JRE instead of the 1.4.2 JRE.

As soon as I did this, I started getting random failures to resolve methods 
from rt.jar. For example, the method Vector#removeElement would be resolved 
but the method Vector#clear would not be resolved.

No methods from java.io.File were resolved. These are just examples, there are 
about 500 errors in the project all of this nature. None of the methods are 
1.4 specific.

The project compiled successfully before I switched to using the 1.3 JRE 
during the build process.

Once this problem appears, you cannot revert to using the 1.4.2 JRE. The 
errors continue to appear. So far, the only recovery I have found is to 
rebuild the workspace from scratch.
Comment 1 Kent Johnson CLA 2003-11-25 12:05:56 EST 
This is very wierd. I suspect your 1.3.1 JRE is corrupted.

Questions:
1. When you create a new workspace, can you build the same projects on top of 
the exact same JRE 1.3.1? Can you then switch to 1.4.2 and back to 1.3.1?
2. In the busted workspace, what happens when you try to browse File or Vector? 
Can you see the methods that do not resolve?
3. Does the method Vector.clear() show up if you search for implementors of 
clear?
Comment 2 Kent Johnson CLA 2003-12-01 10:18:56 EST 
Jonathan: We're going to need your help to track this down.

Please answer the questions above.
Comment 3 Jonathan Gossage CLA 2003-12-01 13:24:15 EST 
We are in the final release cycle for a new product which will finish some 
time this week. Since the problem only occurs when working witjh our 
production code, I will have to hold off until the product is released to 
manufacturing before trying it again.

The one thing that I can add at this time is that the problem could be raised 
using two different JDK's - Sun 1.3.1-09 and Sun 1.3.1-03.
Comment 4 Kent Johnson CLA 2003-12-01 13:30:29 EST 
ok thanks.
Comment 5 Kent Johnson CLA 2004-01-05 10:06:25 EST 
Jonathan: when you get a chance...
Comment 6 Kent Johnson CLA 2004-01-26 14:09:37 EST 
Jonathan: Please reopen when you can provide more info.