Bug 249515 - Compile broken from Europa to Ganymede
Summary: Compile broken from Europa to Ganymede
Status: RESOLVED FIXED
Alias: None
Product: AspectJ
Classification: Tools
Component: Compiler (show other bugs)
Version: 1.6.1   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: aspectj inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-10-02 11:54 EDT by Eddie Mc Greal CLA
Modified: 2008-10-02 12:26 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Eddie Mc Greal CLA 2008-10-02 11:54:06 EDT
When trying to compile a project with Ganymede (AJDT Version: 1.6.0.200809031144
AspectJ version: 1.6.2.20080828190000) I get the error as shown below. The same code compiles with Europa (AJDT Version: 1.5.0.200706070619 AspectJ version: 1.5.4.200705211336)

org.aspectj.weaver.BCException
at org.aspectj.weaver.AjAttribute.read(AjAttribute.java:129)
at org.aspectj.weaver.bcel.BcelAttributes.readAjAttributes(BcelAttributes.java:106)
at org.aspectj.weaver.bcel.BcelMethod.unpackAjAttributes(BcelMethod.java:186)
at org.aspectj.weaver.bcel.BcelMethod.<init>(BcelMethod.java:99)
at org.aspectj.weaver.bcel.BcelObjectType.getDeclaredMethods(BcelObjectType.java:249)
at org.aspectj.weaver.ReferenceType.getD ... :1018)java.io.EOFException
when batch building BuildConfig[/Users/emcgreal/dev/tools/eclipseganymede/Eclipse.app/Contents/MacOS/BkfServer] #Files=103


this is a problem and prevents us from using Ganymede.
Comment 1 Andrew Clement CLA 2008-10-02 12:06:31 EDT
that stack trace indicates a mismatch between a version used to initially build some AspectJ code and a version used to consume it via a later weaving step.

Usually this is because a more recent AspectJ build was used for the initial build and an earlier/previous AspectJ build was used to consume it later.

That doesn't quite seem to be the situation for you though as you are doing things the other way around.

Are you building everything completely from source?  That error indicates you are not but are reading in an aspect from a jar file or other external binary form? Are you using aspectpath?
Comment 2 Eddie Mc Greal CLA 2008-10-02 12:26:39 EDT
Seems it was my problem. I had an old jar file containing the classes on the classpath. After removing it, everything worked fine.