Bug 170617 - Rework AjState management
Summary: Rework AjState management
Status: NEW
Alias: None
Product: AspectJ
Classification: Tools
Component: Compiler (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: aspectj inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-01-16 08:41 EST by Helen Beeken CLA
Modified: 2010-01-26 15:51 EST (History)
2 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 Helen Beeken CLA 2007-01-16 08:41:19 EST 
This comes out of bug 148190.

Currently there is an IncrementalStateManager which holds a map of AjStates to compilerId's. Tools are currently expected to remove the entry for a given compilerId if it's no longer required (in the case of AJDT this is when a project is deleted or closed). However, since bug 148190 there is now an AjCompiler associated with each project. It would be better if that AjCompiler instance knew it's AjState and so when the tool removed it's copy of the AjCompiler for a given project (it's the responsibility of the tool to manage the lifecycles of the AjCompilers) the AjState is consequently removed.