Bug 154339 - AJDT should remove incremental state on project closure and deletion
Summary: AJDT should remove incremental state on project closure and deletion
Status: RESOLVED FIXED
Alias: None
Product: AJDT
Classification: Tools
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 1.4.1   Edit
Assignee: Matthew Ford CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-08-18 06:43 EDT by Helen Beeken CLA
Modified: 2012-04-03 14:16 EDT (History)
0 users

See Also:

Attachments
bug fixed and added a couple of tests (8.09 KB, patch)
2006-09-19 10:36 EDT, Matthew Ford CLA 		no flags Details | Diff
added for when project is converted from an AJ project to java (3.19 KB, patch)
2006-09-20 09:24 EDT, Matthew Ford CLA 		andrew.eisenberg: iplog+
Details | Diff
Show Obsolete (1) 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 Helen Beeken CLA 2006-08-18 06:43:26 EDT 
AJDT should call "IncrementalStateManager.removeIncrementalStateInformationFor(String)" on project closure and deletion otherwise this is not cleared. Currently AJDT only calls this for a given buildConfig name when a user chooses to clean a project. Over time this causes us to hang on to things which are not necessary.
Comment 1 Matthew Ford CLA 2006-09-19 10:36:00 EDT 
Created attachment 50467 [details]
bug fixed and added a couple of tests
Comment 2 Matt Chapman CLA 2006-09-20 06:03:07 EDT 
patch applied. it would also be good to make the same call when the aspectj nature is removed from a project.
Comment 3 Matthew Ford CLA 2006-09-20 09:24:22 EDT 
Created attachment 50556 [details]
added for when project is converted from an AJ project to java
Comment 4 Matthew Ford CLA 2006-09-21 03:16:41 EDT 
fied in  build.204 09/20/2006 and in  build.36 09/20/2006