Community
Participate
Working Groups
It happens when exporting an RCP-Application as a product. Interesting about this error is, that it only occurs when exporting a product and not during the background-compiling that happens when developing and testing right from the IDE. But I'm not sure whether this is because of using eclipse maven integration... The error goes away if i remove usage of @NotNull Annotation (org.jetbrains.annotations.NotNull) in another java file with an interface used by the class where the error occurs. I have not tried to track it down to get minimal steps to reproduce it. I just hope, that the stacktrace below will already help. Content of the log file with the error: # 18.02.09 14:48:59 CET # Eclipse Java Compiler 0.883_R34x, 3.4.1 release, Copyright IBM Corp 2000, 2008. All rights reserved. ---------- 1. WARNING in C:\Dokumente und Einstellungen\jaetzold\workspace\broca-future-project-aggregation\author-app\ag.gaia.broca.authorapp.views\src\ag\gaia\broca\authorapp\editors\BrocaConditionalEditorInputFactory.java (at line 11) @SuppressWarnings({"FieldNameHidesFieldInSuperclass"}) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Unsupported @SuppressWarnings("FieldNameHidesFieldInSuperclass") <snip lots of similar warnings about SuppressWarnings parameters...> ---------- ---------- 18. ERROR in C:\Dokumente und Einstellungen\jaetzold\workspace\broca-future-project-aggregation\author-app\ag.gaia.broca.authorapp.views\src\ag\gaia\broca\authorapp\editors\usertype\SpecialConditionEditorControl.java (at line 0) package ag.gaia.broca.authorapp.editors.usertype; ^ Internal compiler error java.lang.ArrayIndexOutOfBoundsException: 1 at org.eclipse.jdt.internal.compiler.classfmt.MethodInfoWithParameterAnnotations.getParameterAnnotations(MethodInfoWithParameterAnnotations.java:24) at org.eclipse.jdt.internal.compiler.lookup.BinaryTypeBinding.createMethod(BinaryTypeBinding.java:434) at org.eclipse.jdt.internal.compiler.lookup.BinaryTypeBinding.createMethods(BinaryTypeBinding.java:575) at org.eclipse.jdt.internal.compiler.lookup.BinaryTypeBinding.cachePartsFrom(BinaryTypeBinding.java:333) at org.eclipse.jdt.internal.compiler.lookup.LookupEnvironment.createBinaryTypeFrom(LookupEnvironment.java:719) at org.eclipse.jdt.internal.compiler.lookup.LookupEnvironment.createBinaryTypeFrom(LookupEnvironment.java:699) at org.eclipse.jdt.internal.compiler.Compiler.accept(Compiler.java:294) at org.eclipse.jdt.internal.compiler.lookup.LookupEnvironment.askForType(LookupEnvironment.java:102) at org.eclipse.jdt.internal.compiler.lookup.UnresolvedReferenceBinding.resolve(UnresolvedReferenceBinding.java:49) at org.eclipse.jdt.internal.compiler.lookup.BinaryTypeBinding.resolveType(BinaryTypeBinding.java:138) at org.eclipse.jdt.internal.compiler.lookup.BinaryTypeBinding.resolveTypesFor(BinaryTypeBinding.java:916) at org.eclipse.jdt.internal.compiler.lookup.BinaryTypeBinding.getExactMethod(BinaryTypeBinding.java:715) at org.eclipse.jdt.internal.compiler.lookup.Scope.findExactMethod(Scope.java:771) at org.eclipse.jdt.internal.compiler.lookup.Scope.getMethod(Scope.java:2106) at org.eclipse.jdt.internal.compiler.ast.MessageSend.resolveType(MessageSend.java:432) at org.eclipse.jdt.internal.compiler.ast.EqualExpression.resolveType(EqualExpression.java:763) at org.eclipse.jdt.internal.compiler.ast.BinaryExpression.resolveType(BinaryExpression.java:1798) at org.eclipse.jdt.internal.compiler.ast.Expression.resolveTypeExpecting(Expression.java:912) at org.eclipse.jdt.internal.compiler.ast.IfStatement.resolve(IfStatement.java:230) at org.eclipse.jdt.internal.compiler.ast.AbstractMethodDeclaration.resolveStatements(AbstractMethodDeclaration.java:444) at org.eclipse.jdt.internal.compiler.ast.MethodDeclaration.resolveStatements(MethodDeclaration.java:191) at org.eclipse.jdt.internal.compiler.ast.AbstractMethodDeclaration.resolve(AbstractMethodDeclaration.java:403) at org.eclipse.jdt.internal.compiler.ast.TypeDeclaration.resolve(TypeDeclaration.java:1096) at org.eclipse.jdt.internal.compiler.ast.TypeDeclaration.resolve(TypeDeclaration.java:1184) at org.eclipse.jdt.internal.compiler.ast.CompilationUnitDeclaration.resolve(CompilationUnitDeclaration.java:535) at org.eclipse.jdt.internal.compiler.Compiler.process(Compiler.java:743) at org.eclipse.jdt.internal.compiler.ProcessTaskManager.run(ProcessTaskManager.java:137) at java.lang.Thread.run(Thread.java:619) ---------- 1
Is it possible for you to try with 3.5M5? If you would have a test case I could run to reproduce it, this would be really helpful to track it down.
(In reply to comment #1) > Is it possible for you to try with 3.5M5? I already tried, but did not get the maven integration to work. Now that you asked for i gave it another shot with a bit more effort and got maven to work. The good result: The error does not occur when exporting the product with e3.5M5. :-) I used 3.4.1 as target platform for both. So this may be considered a "fixed" bug for 3.5? > If you would have a test case I could run to reproduce it, this would be really > helpful to track it down. Yes, i thought so too, but do not have one available, sorry.
Closing since 3.5M5 works for Stephan
Verified by the reporter
