Community
Participate
Working Groups
The following stack trace is observed when attempting to self-compile Cheetah03. This error can also be triggered by attempting to compile org.apache.joran.InterpreterTest from the CVS sources for Apache Log4j. Internal compiler error java.lang.Error: Undefined base type: . at org.eclipse.jdt.internal.compiler.lookup.LookupEnvironment.getTypeFromSignature (LookupEnvironment.java:636) at org.eclipse.jdt.internal.compiler.lookup.LookupEnvironment.getTypeFromTypeSigna ture(LookupEnvironment.java:678) at org.eclipse.jdt.internal.compiler.lookup.BinaryTypeBinding.cachePartsFrom (BinaryTypeBinding.java:200) at org.eclipse.jdt.internal.compiler.lookup.LookupEnvironment.createBinaryTypeFrom (LookupEnvironment.java:317) at org.eclipse.jdt.internal.compiler.lookup.LookupEnvironment.createBinaryTypeFrom (LookupEnvironment.java:297) at org.eclipse.jdt.internal.compiler.Compiler.accept(Compiler.java:191) at org.eclipse.jdt.internal.compiler.lookup.LookupEnvironment.askForType (LookupEnvironment.java:81) at org.eclipse.jdt.internal.compiler.lookup.UnresolvedReferenceBinding.resolve (UnresolvedReferenceBinding.java:43) at org.eclipse.jdt.internal.compiler.lookup.BinaryTypeBinding.resolveType (BinaryTypeBinding.java:49) at org.eclipse.jdt.internal.compiler.lookup.BinaryTypeBinding.memberTypes (BinaryTypeBinding.java:577) at org.eclipse.jdt.internal.compiler.lookup.ParameterizedTypeBinding.memberTypes (ParameterizedTypeBinding.java:404) at org.eclipse.jdt.internal.compiler.lookup.ParameterizedTypeBinding.getMemberType (ParameterizedTypeBinding.java:270) at org.eclipse.jdt.internal.compiler.lookup.Scope.findMemberType (Scope.java:612) at org.eclipse.jdt.internal.compiler.lookup.Scope.getTypeOrPackage (Scope.java:1641) at org.eclipse.jdt.internal.compiler.lookup.Scope.getType (Scope.java:1511) at org.eclipse.jdt.internal.compiler.ast.SingleTypeReference.getTypeBinding (SingleTypeReference.java:38) at org.eclipse.jdt.internal.compiler.ast.TypeReference.resolveType (TypeReference.java:140) at org.eclipse.jdt.internal.compiler.ast.TypeReference.resolveSuperType (TypeReference.java:93) at org.eclipse.jdt.internal.compiler.lookup.ClassScope.findSupertype (ClassScope.java:895) at org.eclipse.jdt.internal.compiler.lookup.ClassScope.connectSuperInterfaces (ClassScope.java:677) at org.eclipse.jdt.internal.compiler.lookup.ClassScope.connectTypeHierarchy (ClassScope.java:731) at org.eclipse.jdt.internal.compiler.lookup.ClassScope.connectMemberTypes (ClassScope.java:607) at org.eclipse.jdt.internal.compiler.lookup.ClassScope.connectTypeHierarchy (ClassScope.java:736) at org.eclipse.jdt.internal.compiler.lookup.ClassScope.connectMemberTypes (ClassScope.java:607) at org.eclipse.jdt.internal.compiler.lookup.ClassScope.connectTypeHierarchy (ClassScope.java:736) at org.eclipse.jdt.internal.compiler.lookup.CompilationUnitScope.connectTypeHierar chy(CompilationUnitScope.java:236) at org.eclipse.jdt.internal.compiler.lookup.LookupEnvironment.completeTypeBindings (LookupEnvironment.java:177) at org.eclipse.jdt.internal.compiler.Compiler.beginToCompile (Compiler.java:305) at org.eclipse.jdt.internal.compiler.Compiler.compile (Compiler.java:319) at org.eclipse.jdt.internal.core.builder.AbstractImageBuilder.compile (AbstractImageBuilder.java:209) at org.eclipse.jdt.internal.core.builder.AbstractImageBuilder.compile (AbstractImageBuilder.java:159) at org.eclipse.jdt.internal.core.builder.BatchImageBuilder.build (BatchImageBuilder.java:49) at org.eclipse.jdt.internal.core.builder.JavaBuilder.buildAll (JavaBuilder.java:212) at org.eclipse.jdt.internal.core.builder.JavaBuilder.build (JavaBuilder.java:140) at org.eclipse.core.internal.events.BuildManager$2.run (BuildManager.java:514) at org.eclipse.core.internal.runtime.InternalPlatform.run (InternalPlatform.java:607) at org.eclipse.core.runtime.Platform.run(Platform.java:524) at org.eclipse.core.internal.events.BuildManager.basicBuild (BuildManager.java:140) at org.eclipse.core.internal.events.BuildManager.basicBuild (BuildManager.java:227) at org.eclipse.core.internal.events.BuildManager.basicBuild (BuildManager.java:168) at org.eclipse.core.internal.events.BuildManager$1.run (BuildManager.java:197) at org.eclipse.core.internal.runtime.InternalPlatform.run (InternalPlatform.java:607) at org.eclipse.core.runtime.Platform.run(Platform.java:524) at org.eclipse.core.internal.events.BuildManager.basicBuild (BuildManager.java:200) at org.eclipse.core.internal.events.BuildManager.basicBuildLoop (BuildManager.java:245) at org.eclipse.core.internal.events.BuildManager.build (BuildManager.java:273) at org.eclipse.core.internal.events.AutoBuildJob.doBuild (AutoBuildJob.java:133) at org.eclipse.core.internal.events.AutoBuildJob.run (AutoBuildJob.java:164) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:62) FieldDeclarationMatch.java org.eclipse.jdt.core/search/org/eclipse/jdt/core/search line 0 April 17, 2004 5:34:28 PM
Created attachment 9623 [details] complete workspace .log file
I'd just like to say I got this issue as well, compiling my own code using win32 build I200404131323 and Cheetah03. The compile works fine if source code compatability is set to '1.4', but dies on the first class it sees if set to '1.5', with a stack trace similar to the one already given. I've tried restarting Eclipse a few times- unfortunately it hasn't helped. thanks Roberto
Cannot reproduce when compiling Cheetah03 with Cheetah03.
Paul, Please provide detailed steps to reproduce. Also make sure that you apply Cheetah-03 to a clean Eclipse SDK. There seems to be issues in update support, where multiple versions of Cheetah are interfering with each other.
Detailed instructions to reproduce: 1. install jdk 1.5 C:\Program Files>java -version java version "1.5.0-beta" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0-beta-b32c) Java HotSpot(TM) Client VM (build 1.5.0-beta-b32c, mixed mode) 2. install fresh copy of I20040407 in C:\Program Files\ Eclipse Platform Version: 3.0.0 Build id: 200404071337 3. start "C:\Program Files\eclipse\eclipse.exe" -vmargs -Xmx768m 4. install cheeta03 using update manager 5. restart workbench 6. switch to java perspective 7. stop workbench 8. start workbench 9. set workbench compiler complience level to 1.5 (default settings) 10. check-out project org.eclipse.jdt.core v_422_Cheetah03 from CVS
I think it is a bug in JDK1.5 libraries. I tried again with latest Cheetah (04) and clean build, and couldn't reproduce the problem using a more recent JDK1.5 delivery. I think early libraries had inconsistent signatures, which got resolved since then (using build 1.5.0-beta2-b47, mixed mode).
Could be, but I'll have to wait for a public release of beta-2 before I can verify. I still the same behavior with Cheetah04 and Eclipse Build id: 200404281424.
Or it could be a dup of bug 59983, if further incremental compilations got triggered.
This is still present in Cheetah05/Eclipse3.0M9, so its not a dup of bug 55903.
Then please provide exact steps to reproduce. I don't mean how you install the Cheetah, but rather how you configure some offending project, and get it to compile. I can compile jdt/core without any problem with the Cheetah.
Please reopen once info got added.
I have upgraded to JDK 1.5.0-beta2-b51, and this does indeed fix the problem.
