Bug 482556 - BCException in AjState.recordClassFile(AjState.java:1519)
Summary: BCException in AjState.recordClassFile(AjState.java:1519)
Status: NEW
Alias: None
Product: AspectJ
Classification: Tools
Component: IDE (show other bugs)
Version: unspecified   Edit
Hardware: PC Mac OS X
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: aspectj inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-11-19 03:09 EST by victor Ni CLA
Modified: 2016-03-08 11:43 EST (History)
1 user (show)

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 victor Ni CLA 2015-11-19 03:09:22 EST 
org.aspectj.weaver.BCException
at org.aspectj.ajdt.internal.core.builder.AjState.recordClassFile(AjState.java:1519)
at org.aspectj.ajdt.internal.core.builder.AjState.noteResult(AjState.java:1325)
at org.aspectj.ajdt.internal.core.builder.AjBuildManager$3.acceptResult(AjBuildManager.java:1066)
at org.aspectj.ajdt.internal.compiler.AjPipeliningCompilerAdapter.afterProcessing(AjPipeliningCompilerAdapter.java:426)
at org.aspectj.ajdt.internal.co ... 5.20150128171000.jar:/Users/xinfeng/tools/eclipse/Eclipse.app/Contents/MacOS//../../../plugins/org.eclipse.equinox.launcher_1.3.0.v20140415-2008.jar:
Comment 1 Andrew Clement CLA 2015-11-23 18:32:22 EST 
This has been seen before but the only reason has been when the source code temporarily had an error in it. In the particular failing scenario an annotation value was not being used correctly. The JDT had a bug in it such that even though it tries its best to create a class file for broken code, it was creating a broken class file in this case and the AjState manager noticed immediately that the class was nonsense.  When you see this happening - do you have errors somewhere in your source code? I thought all the variations of the annotation situation had been fixed, but there may be some other kind of error that causes the same problem.