Bug 55134 - Incremental compilation does not delete weaver-generated class files
Summary: Incremental compilation does not delete weaver-generated class files
Status: RESOLVED FIXED
Alias: None
Product: AspectJ
Classification: Tools
Component: Compiler (show other bugs)
Version: 1.2   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 1.2   Edit
Assignee: Adrian Colyer CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-03-17 14:09 EST by Adrian Colyer CLA
Modified: 2004-03-18 09:40 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 Adrian Colyer CLA 2004-03-17 14:09:38 EST 
During incremental compilation, AjState records classes generated from source 
files following the initial compile phase, but before weaving. (So that these 
can be passed to the weaver on a subsequent iteration if we need to reweave the 
world). During weaving of a given class file, the weaver may generate additional 
class files (for e.g. around closures) that get written to the output. If the 
orginal source file is deleted, these additional weaver generated classes are 
not deleted from the output since AjState does not know about them.
Comment 1 Adrian Colyer CLA 2004-03-18 09:40:35 EST 
Fixed in tree. UnwovenClassFile.deleteRealFile now deletes the class file plus 
any $Ajc*.class extensions of it.