Bug 482556

Summary:	BCException in AjState.recordClassFile(AjState.java:1519)
Product:	[Tools] AspectJ	Reporter:	victor Ni <findnxf>
Component:	IDE	Assignee:	aspectj inbox <aspectj-inbox>
Status:	NEW ---	QA Contact:
Severity:	major
Priority:	P3	CC:	aclement
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Mac OS X
Whiteboard:

Description victor Ni

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

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.