Bug 17807 - Incremental build problems deleting secondary types
Summary: Incremental build problems deleting secondary types
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.0   Edit
Hardware: PC All
: P3 normal (vote)
Target Milestone: 2.0 F2   Edit
Assignee: Jerome Lanneluc CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-05-24 15:31 EDT by Kent Johnson CLA
Modified: 2002-06-03 09:49 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kent Johnson CLA 2002-05-24 15:31:55 EDT
We had 2 order dependent problems deleting secondary types... in the first when 
a source file was compiled before the secondary type was deleted, it did not 
think it was missing. In the second, we aborted the build because we could not 
find the .class file. Both are fixed by deleting secondary types at the end of 
the compile loop & removing the previousLocations optimization.

Start by building the following types, then turn off auto-build:

AA.java:
public class AA {}
class AZ {}

AB.java : public class AB extends AZ {}

BB.java :
public class BB {
 void foo() {
  System.out.println(new AB());
  System.out.println(new ZA());}}

ZZ.java :
public class ZZ {}
class ZA {}

Case 1: Comment out AZ and touch the file BB.
Case 2: Comment out ZA and touch the file BB.
Comment 1 Kent Johnson CLA 2002-05-24 15:34:20 EDT
Both problems are fixed by deleting secondary types at the end of the compile 
loop & removing the previousLocations optimization.
Comment 2 Jerome Lanneluc CLA 2002-06-03 09:49:10 EDT
Verified