Community
Participate
Working Groups
java.lang.ArrayIndexOutOfBoundsException at org.aspectj.org.eclipse.jdt.internal.compiler.ast.AbstractMethodDeclaration.bindArguments(AbstractMethodDeclaration.java:95) at org.aspectj.org.eclipse.jdt.internal.compiler.ast.AbstractMethodDeclaration.resolve(AbstractMethodDeclaration.java:422) at org.aspectj.org.eclipse.jdt.internal.compiler.ast.TypeDeclaration.resolve(TypeDeclaration.java:1182) at org.aspectj.org.eclipse.jdt.internal.compi ... ob.run(AutoBuildJob.java:241) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) Compile error: ArrayIndexOutOfBoundsException thrown: 0 Get this error when compiling my project, then this exception orrurs: org.aspectj.org.eclipse.jdt.internal.compiler.problem.AbortCompilation at org.aspectj.org.eclipse.jdt.internal.compiler.problem.ProblemHandler.handle(ProblemHandler.java:121) at org.aspectj.org.eclipse.jdt.internal.compiler.problem.ProblemHandler.handle(ProblemHandler.java:179) at org.aspectj.org.eclipse.jdt.internal.compiler.problem.ProblemReporter.handle(ProblemReporter.java:2070) at org.aspectj.org.eclipse.jdt.internal.compiler.proble ... ck(android.view.View)) end public void onClick(android.view.View) Then this windows pops up: org.aspectj.org.eclipse.jdt.internal.compiler.problem.AbortCompilation at org.aspectj.org.eclipse.jdt.internal.compiler.problem.ProblemHandler.handle(ProblemHandler.java:121) at org.aspectj.org.eclipse.jdt.internal.compiler.problem.ProblemHandler.handle(ProblemHandler.java:179) at org.aspectj.org.eclipse.jdt.internal.compiler.problem.ProblemReporter.handle(ProblemReporter.java:2070) at org.aspectj.org.eclipse.jdt.internal.compiler.proble ... RETURN end protected volatile void onSuccess(Object) Eclipse: Version: Juno Service Release 2 Build id: 20130225-0426 AspetJ: Version: 2.2.3.e42x-RELEASE-20130625-1400 AspectJ version: 1.7.3.20130613144500-a
I know this bug is old... sorry I'm only just getting to it. If you do want me to dig into it then it'd be great to see a sample project that has this problem, or even try building it with a recent AspectJ 1.8 to see if this problem is already fixed.