Bug 98281

Summary:	Structure model from incremental build shows all relationships coming from injars
Product:	[Tools] AspectJ	Reporter:	Helen Beeken <hlhawkins>
Component:	Compiler	Assignee:	Andrew Clement <aclement>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3
Version:	unspecified
Target Milestone:	1.5.1
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Helen Beeken

2005-06-03 10:46:53 EDT

To reproduce in AJDT:

1. uncomment the Structure Model view in the ajdt.ui plugin.xml and have this
   view showing
2. Install the Telecom Example
3. Activate the billing.ajproperties build configuration
4. Open "Timing.aj" in the editor
5. Paste the following into the line below the aspect declaration:

declare warning : call(void Connection.drop()) : "call to Connection.drop"

   (this has to be the first entry in the aspect)

6. Press Ctrl+S to save
7. The contents of the structure model view says that all the relationships come
from injar aspects.

Doing a full build fixes this. Plus, once you've done a full build you can't
reproduce this problem with the same project.

This is fairly serious as far as AJDT is concerned since in this case our views
and markers don't show any relationships.

Comment 1 Andrew Clement

2005-06-03 12:55:14 EDT

'injar aspect' means 'binary input' - usually in this case it means the input
was bytecode.  This happens in incremental mode because we don't go back to sort
when compiling, we use the bytecode that is cached after the previous compile
and weave into *it*.  I'm working on changing the compile loop to always go back
to source, in order to fix our memory problems, a side effect will be that this
bug gets fixed.

Comment 2 Helen Beeken

2006-02-21 09:37:40 EST

This bug has been fixed by the changes put in to always go back to source if changes have been made to an aspect. I've tested this within AJDT after generating a new aspectj with these latest fixes in it.

Comment 3 Andrew Clement

2006-02-21 10:41:23 EST

ok :)