Error with aspectj 1.6.9 after cobertura instrumentation
--------------------------------------------------------
Key: MCOBERTURA-127
URL: http://jira.codehaus.org/browse/MCOBERTURA-127
Project: Maven 2.x Cobertura Plugin
Issue Type: Bug
Affects Versions: 2.4
Environment: aspectj 1.6.9
aspectj-maven-plugin 1.3
Reporter: Julien HENRY
Attachments: aspectj-1.6.9-it.patch
See attached IT.
It seems there is a change in aspectj 1.6.9 that broke integration with
cobertura (maybe class file compression [1]).
After cobertura has instrumented source code, aspectj fail to weave aspects.
Here is an extract of the error:
{code}
[ERROR] Failed to execute goal
org.codehaus.mojo:aspectj-maven-plugin:1.3:test-compile (aspectj) on project
aspectj-it: Compiler errors:
abort ABORT -- (BCException) malformed org.aspectj.weaver.EffectiveSignature
attribute (length:27)org.aspectj.weaver.BCException: Bad type signature <init>
when batch building BuildConfig[null] #Files=2 AopXmls=#0
when batch building BuildConfig[null] #Files=2 AopXmls=#0
malformed org.aspectj.weaver.EffectiveSignature attribute
(length:27)org.aspectj.weaver.BCException: Bad type signature <init>
when batch building BuildConfig[null] #Files=2 AopXmls=#0
when batch building BuildConfig[null] #Files=2 AopXmls=#0
org.aspectj.weaver.BCException: malformed org.aspectj.weaver.EffectiveSignature
attribute (length:27)org.aspectj.weaver.BCException: Bad type signature <init>
when batch building BuildConfig[null] #Files=2 AopXmls=#0
when batch building BuildConfig[null] #Files=2 AopXmls=#0
at org.aspectj.weaver.AjAttribute.read(AjAttribute.java:137)
at org.aspectj.weaver.bcel.Utility.readAjAttributes(Utility.java:101)
at
org.aspectj.weaver.bcel.BcelMethod.unpackAjAttributes(BcelMethod.java:184)
at org.aspectj.weaver.bcel.BcelMethod.<init>(BcelMethod.java:91)
[...]
{code}
Note that it seems to occurs only when I use
{code}MethodSignature signature = (MethodSignature) jp.getSignature();{code}
in my aspect.
I will open the same bug in aspectj and cobertura bug trackers as I think this
is not a issue of the plugin itself (but it was easier to produce an
integration test with Maven). Therefore I have no idea if it is an aspectj or
cobertura issue.
[1] http://eclipse.org/aspectj/doc/released/README-169.html
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
