Bug 260948 - Structure model does not contain aspects on aspect path in certain cases
Summary: Structure model does not contain aspects on aspect path in certain cases
Status: RESOLVED DUPLICATE of bug 265729
Alias: None
Product: AspectJ
Classification: Tools
Component: Build (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: 1.6.4   Edit
Assignee: aspectj inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-13 18:45 EST by Andrew Eisenberg CLA
Modified: 2009-02-24 18:36 EST (History)
1 user (show)

See Also:

Attachments
pair of projects where this happens (5.19 KB, application/octet-stream)
2009-01-13 18:46 EST, Andrew Eisenberg CLA 		no flags Details
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 Andrew Eisenberg CLA 2009-01-13 18:45:28 EST 
When a project is not directly advised by an aspect on an aspect path, but does contain some ITDs because it implements an interface with ITDs on it, the advising aspect should be faulted into the model, but it is not.

There may be other cases where such an aspect should be faulted into the model, but is not.
Comment 1 Andrew Eisenberg CLA 2009-01-13 18:46:44 EST 
Created attachment 122474 [details]
pair of projects where this happens

These two projects illustrate this problem.
Comment 2 Andrew Eisenberg CLA 2009-01-13 18:47:58 EST 
The Aspects Declarations relationship is in the relationship manager, but the target is an incomplete AspectJ element handle.
Comment 3 Andrew Clement CLA 2009-01-13 19:32:34 EST 
Actually we do go looking for the aspects on the aspectpath so it may be sensible to fault them in when we first discover them.
Comment 4 Andrew Clement CLA 2009-02-24 18:36:50 EST 
faulting in for aspects only in affect due to ITDs is implemented under bug 265729

*** This bug has been marked as a duplicate of bug 265729 ***