Bug 84030 - related location and abstract pointcuts
Summary: related location and abstract pointcuts
Status: RESOLVED DUPLICATE of bug 78615
Alias: None
Product: AJDT
Classification: Tools
Component: UI (show other bugs)
Version: 1.2.0 M2   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: AJDT-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-01-31 06:26 EST by Wes Isberg CLA
Modified: 2005-02-03 12:31 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Wes Isberg CLA 2005-01-31 06:26:48 EST
An issue you're no-doubt aware of: the "related location" for a declare error
might not identify the concrete aspect that defined the pointcut at issue, so
the user will have to hunt for it.

public class Const {
	public static void main(String[] args) {		
	}
	static abstract aspect A {
		protected abstract pointcut pc();
		declare error: execution(* *(..)) && pc() : "error";
	}
        // same join point, but you get the idea...
	static aspect B extends A {
		protected pointcut pc() : within(Const) && execution(static * *(..));
	}
	static aspect C extends A {
		protected pointcut pc() : within(Const) && execution(public * *(..));
	}
}
Comment 1 Mik Kersten CLA 2005-02-03 12:31:52 EST
This is addressed by an AspectJ enhancement report that's a high-priority on 
my list.  As described there it will be resolved by adding a "concretized by" 
relationship to the ASM.

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