Community
Participate
Working Groups
An internal error occurred during: "Computing type hierarchy of 'FunctionDescriptorBuilder<ST> - com.siemens.spice.hscm.diagram.impl.base'...". org.eclipse.jdt.internal.compiler.env.NameEnvironmentAnswer.<init>([Lorg/eclipse/jdt/internal/compiler/env/ISourceType;Lorg/eclipse/jdt/internal/compiler/env/AccessRestriction;)V
I installed ajdt from AspectJ features and related tools - http://download.eclipse.org/tools/ajdt/45/dev/update maybe this is the problem ... now i will try use the one from AspectJ features and related tools - http://download.eclipse.org/tools/ajdt/46/dev/update
new (46) is not possible to install ... p2 doesn't allowed this because "a newer version is already installed" :-/
Moving to AJDT for comments, not sure whether an Neon-compatible, official release is available. At least in the following thread s.o. succeeded in installing AJDT in Neon: https://www.eclipse.org/forums/index.php/t/1072534/ - note the mention of "first uninstall". Do you have more details on the "internal error"? Please check your error log for a stack trace or other information.
(In reply to Stephan Herrmann from comment #3) > Moving to AJDT for comments, not sure whether an Neon-compatible, official > release is available. At least in the following thread s.o. succeeded in > installing AJDT in Neon: https://www.eclipse.org/forums/index.php/t/1072534/ > - note the mention of "first uninstall". > > Do you have more details on the "internal error"? Please check your error > log for a stack trace or other information. That worked for me ... thxs ... it would be nice if this 46 version is part of the "normal" eclipse version :)
I modified the AJDT downloads page to include proper references to the dev builds for Eclipse 4.5 and 4.6. Haven't had the bandwidth to do a formal release in a while but a formal release is just a dev build with a different label on it - they both get the same amount of testing.
Happens to me under Eclipse 4.10.0 build 20181214-0600. I had an instance of the NIO.2 BasicFileAttributes, and wanted to see what other classes besides POSIX were supported by default. So I clicked on the 'BasicFileAttributes' identifier and hit Ctrl-T; an empty window appeared. (It *should* have at least mentioned PosixFileAttributes as a subclass.) Confused, I tried clicking on the identifier and hitting F4, and that's when the error dialog appeared: An internal error occurred during: "Computing type hierarchy of 'BasicFileAttributes - java.nio.file.attribute'...". begin 37, end 36, length 79 Below is the dump from the logfile. !ENTRY org.eclipse.core.jobs 4 2 2019-08-29 15:57:02.071 !MESSAGE An internal error occurred during: "Computing type hierarchy of 'BasicFileAttributes - java.nio.file.attribute'...". !STACK 0 java.lang.StringIndexOutOfBoundsException: begin 37, end 36, length 79 at java.base/java.lang.String.checkBoundsBeginEnd(String.java:3116) at java.base/java.lang.String.substring(String.java:1885) at org.eclipse.jdt.internal.core.util.HandleFactory.createOpenable(HandleFactory.java:108) at org.eclipse.jdt.internal.core.hierarchy.IndexBasedHierarchyBuilder.buildFromPotentialSubtypes(IndexBasedHierarchyBuilder.java:338) at org.eclipse.jdt.internal.core.hierarchy.IndexBasedHierarchyBuilder.build(IndexBasedHierarchyBuilder.java:165) at org.eclipse.jdt.internal.core.hierarchy.TypeHierarchy.compute(TypeHierarchy.java:323) at org.eclipse.jdt.internal.core.hierarchy.TypeHierarchy.refresh(TypeHierarchy.java:1319) at org.eclipse.jdt.internal.core.CreateTypeHierarchyOperation.executeOperation(CreateTypeHierarchyOperation.java:94) at org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:736) at org.eclipse.jdt.internal.core.JavaModelOperation.runOperation(JavaModelOperation.java:802) at org.eclipse.jdt.internal.core.BinaryType.newTypeHierarchy(BinaryType.java:898) at org.eclipse.jdt.internal.core.BinaryType.newTypeHierarchy(BinaryType.java:857) at org.eclipse.jdt.internal.ui.typehierarchy.TypeHierarchyLifeCycle.createTypeHierarchy(TypeHierarchyLifeCycle.java:304) at org.eclipse.jdt.internal.ui.typehierarchy.TypeHierarchyLifeCycle.doHierarchyRefresh(TypeHierarchyLifeCycle.java:335) at org.eclipse.jdt.internal.ui.typehierarchy.TypeHierarchyLifeCycle.doHierarchyRefreshBackground(TypeHierarchyLifeCycle.java:275) at org.eclipse.jdt.internal.ui.typehierarchy.TypeHierarchyLifeCycle$2.run(TypeHierarchyLifeCycle.java:228) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
