Summary: | interface initializer order is wrong | ||
---|---|---|---|
Product: | [Tools] AspectJ | Reporter: | George Harley <gharley> |
Component: | Compiler | Assignee: | Adrian Colyer <adrian.colyer> |
Status: | REOPENED --- | QA Contact: | |
Severity: | normal | ||
Priority: | P5 | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Windows 2000 | ||
Whiteboard: |
Description
George Harley
2003-04-23 04:44:22 EDT
The NoAspectBoundException is a correct change in AspectJ-1.1 and is documented in the readme: http://dev.eclipse.org/viewcvs/indextech.cgi/~checkout~/aspectj-home/README- 11.html#ASPECT_INSTANTIATION_AND_ADVICE The order of the interface initializers you're seeing is a bug, but I don't believe it is critical, so I'm leaving it as a P3. If it turns out to be easy to fix it should be resolved for 1.1rc2. A test case has been added to ajcTestsFailing.xml. The 1.2 target milestone has been removed. After analysis, this bug is tightly coupled with the implementation of initialization join points. This implementation is complicated and I'm very wary of changing it to fix a bug this small. We're not going to get to this in AJ 1.5.0. Marking as "LATER" for consideration in 1.5.1 and future release planning. No-one else has run into this issue that I'm aware of in the 2.5 years since it was first raised so this is not a high-priority problem right now. LATER/REMIND bugs are being automatically reopened as P5 because the LATER and REMIND resolutions are deprecated. |