185451 – [ataspectj] Abstract Aspect with @AspectJ concrete Aspect: IllegalAccessError

Bug 185451 - [ataspectj] Abstract Aspect with @AspectJ concrete Aspect: IllegalAccessError

Summary: [ataspectj] Abstract Aspect with @AspectJ concrete Aspect: IllegalAccessError

Status:	RESOLVED FIXED

Alias:	None

Product:	AspectJ
Classification:	Tools
Component:	Compiler (show other bugs)
Version:	DEVELOPMENT
Hardware:	PC Linux

Importance:	P3 normal (vote)
Target Milestone:	1.6.1
Assignee:	aspectj inbox
QA Contact:

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2007-05-03 17:34 EDT by John D. Heintz
Modified:	2008-06-11 17:09 EDT (History)
CC List:	1 user (show)

See Also:

Attachments
Set of Eclipse projects to demonstrate success/failure for this (8.05 KB, application/zip) 2007-05-03 17:36 EDT, John D. Heintz	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 John D. Heintz

2007-05-03 17:34:17 EDT

Given an abstract library aspect (code-style) I'm trying to create a concrete @AspectJ aspect to apply it to the local project.

I'm getting the following stack trace at runtime:
Exception in thread "main" java.lang.IllegalAccessError: tried to access method com.the.enterprise.logging.Logging.ajc$around$com_the_enterprise_logging_Logging$1$18006b3eproceed(Lorg/aspectj/runtime/internal/AroundClosure;)Ljava/lang/Object; from class com.the.enterprise.service.Service
	at com.the.enterprise.service.Service.doSomething_aroundBody1$advice(Service.java:110)
	at com.the.enterprise.service.Service.doSomething(Service.java:1)
	at com.the.enterprise.service.Main.main(Main.java:11)

Comment 1 John D. Heintz

2007-05-03 17:36:20 EDT

Created attachment 65857 [details]
Set of Eclipse projects to demonstrate success/failure for this

Comment 2 Andrew Clement

2008-06-11 17:09:43 EDT

I believe this is another occurrence of the bug where mixing styles just didn't work.  I've recreated the failure with AspectJ1.5.2a using the attached samples and confirmed that it works just fine with 1.6.0 and the latest 1.6.1 dev builds.