Bug 91509 - Cannot use precompiled Aspect-JARS because of exception
Summary: Cannot use precompiled Aspect-JARS because of exception
Status: RESOLVED FIXED
Alias: None
Product: AJDT
Classification: Tools
Component: Core (show other bugs)
Version: 1.2.0 M2   Edit
Hardware: PC Linux
: P3 blocker (vote)
Target Milestone: ---   Edit
Assignee: AJDT-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-04-15 07:47 EDT by Simon Heinzle CLA
Modified: 2005-06-29 06:44 EDT (History)
0 users

See Also:

Attachments
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 Simon Heinzle CLA 2005-04-15 07:47:15 EDT 
Following setup:

Precompiled JAR File containing an abstract aspect (especially an abstract
pointcut) -- JAR was precompiled using ajc version 1.2.1

Aspect-Project in Eclipse, extending the abstract aspect to a concrete one using
this JAR  file in the AspectJ Aspect Path. 

AJDT 1.2.0M2 produces following error: "BCException thrown: malformed
org.aspectj.weaver.PointcutDeclaration attribute java.IO.EOFException"

AJDT 1.1.12 produces following error: "BCException thrown: unknown attribute
org.aspectj.weaver.WeaverVersion"
Comment 1 Andrew Clement CLA 2005-04-15 08:41:18 EDT 
AspectJ1.2.1 introduced the WeaverVersion attribute to help with migration
issues (ironically).

AspectJ1.1.12 isn't expecting the attribute because 1.1.12 contains AspectJ1.2.0

AspectJ1.2.0M2 isn't able to process the PointcutDeclaration attribute because
1.2.0M2 includes AspectJ1.5.0M1 which expanded type patterns to include an
'annotationpattern' which is of course missing from what you built with
AspectJ1.2.1.

Now the *good* news - I fixed this problem in January, under bug 82134.  The fix
is in AspectJ1.5.0M2 and that version of AspectJ is in AJDT1.2.0M3 that was
released earlier this week.
Comment 2 Matt Chapman CLA 2005-06-29 06:44:29 EDT 
As per Andy's comments above, this is fixed in more recent versions of AspectJ