Databases
StackOverflow2013
Postsdbo
POEclipse (Kepler) Workspace acting weird (type hierarchy, searching for references not working)
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POEclipse (Kepler) Workspace acting weird (type hierarchy, searching for references not working)
    primarykey
    data
    text
    <p>Using Eclipse Kepler Running on Windows 7 (64-Bit), my workspace is acting weird.</p> <p>The following is not working (workspace wide):</p> <ul> <li>Type hierarchy of a class / method is showing up empty</li> <li>searching for references</li> </ul> <p>Have tried to </p> <ul> <li>Rebuilding / Cleaning / Closing &amp; Opening Projects</li> <li>Restart Eclipse</li> <li>Reboot</li> <li>Boot Eclipse in Clean mode (-clean)</li> <li>Clear out indexes manually</li> </ul> <p>The <strong>only</strong> thing that has worked so far is switching to a new workspace and checking out one of my projects there. However, this is very suboptimal, since I have a certain amount of projects and settings in my current workspace.</p> <p><strong>EDIT - Stack Trace</strong></p> <p>I'm getting the following stack trace when I specifically "Focus On" in Type Hierarchy view:</p> <pre><code>!ENTRY org.eclipse.core.jobs 4 2 2013-12-19 15:08:39.156 !MESSAGE An internal error occurred during: "Computing type hierarchy of 'String - java.lang'...". !STACK 0 java.lang.NullPointerException at org.eclipse.core.runtime.Path.&lt;init&gt;(Path.java:183) at org.eclipse.core.internal.resources.WorkspaceRoot.getProject(WorkspaceRoot.java:182) at org.eclipse.jdt.internal.core.JavaModel.getJavaProject(JavaModel.java:189) at org.eclipse.jdt.internal.core.search.IndexSelector.getJavaProject(IndexSelector.java:286) at org.eclipse.jdt.internal.core.search.IndexSelector.initializeIndexLocations(IndexSelector.java:217) at org.eclipse.jdt.internal.core.search.IndexSelector.getIndexLocations(IndexSelector.java:276) at org.eclipse.jdt.internal.core.search.JavaSearchParticipant.selectIndexURLs(JavaSearchParticipant.java:121) at org.eclipse.jdt.internal.core.search.PatternSearchJob.getIndexes(PatternSearchJob.java:84) at org.eclipse.jdt.internal.core.search.SubTypeSearchJob.getIndexes(SubTypeSearchJob.java:33) at org.eclipse.jdt.internal.core.search.PatternSearchJob.ensureReadyToRun(PatternSearchJob.java:52) at org.eclipse.jdt.internal.core.search.processing.JobManager.performConcurrentJob(JobManager.java:174) at org.eclipse.jdt.internal.core.hierarchy.IndexBasedHierarchyBuilder.searchAllPossibleSubTypes(IndexBasedHierarchyBuilder.java:523) at org.eclipse.jdt.internal.core.hierarchy.IndexBasedHierarchyBuilder.determinePossibleSubTypes(IndexBasedHierarchyBuilder.java:406) at org.eclipse.jdt.internal.core.hierarchy.IndexBasedHierarchyBuilder.build(IndexBasedHierarchyBuilder.java:120) at org.eclipse.jdt.internal.core.hierarchy.TypeHierarchy.compute(TypeHierarchy.java:300) at org.eclipse.jdt.internal.core.hierarchy.TypeHierarchy.refresh(TypeHierarchy.java:1267) at org.eclipse.jdt.internal.core.CreateTypeHierarchyOperation.executeOperation(CreateTypeHierarchyOperation.java:90) at org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:728) at org.eclipse.jdt.internal.core.JavaModelOperation.runOperation(JavaModelOperation.java:788) at org.eclipse.jdt.internal.core.BinaryType.newTypeHierarchy(BinaryType.java:918) at org.eclipse.jdt.internal.core.BinaryType.newTypeHierarchy(BinaryType.java:876) at org.eclipse.jdt.internal.ui.typehierarchy.TypeHierarchyLifeCycle.createTypeHierarchy(TypeHierarchyLifeCycle.java:299) at org.eclipse.jdt.internal.ui.typehierarchy.TypeHierarchyLifeCycle.doHierarchyRefresh(TypeHierarchyLifeCycle.java:330) at org.eclipse.jdt.internal.ui.typehierarchy.TypeHierarchyLifeCycle.doHierarchyRefreshBackground(TypeHierarchyLifeCycle.java:271) at org.eclipse.jdt.internal.ui.typehierarchy.TypeHierarchyLifeCycle$2.run(TypeHierarchyLifeCycle.java:224) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) </code></pre> <p>Anyone?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USbknopper
    1. USbknopper
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POEclipse (Kepler) Workspace acting weird (type hierarchy, searching for references not working)
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI had a similar problem at work once, except EVERYTHING was missing. Not only the type hierarchy, but the packages in the project explorer, etc. IIRC it had something to do with the .metadata folder. EDIT: Perhaps this thread will help: http://stackoverflow.com/questions/16354028/eclipse-type-hierarchy-not-always-working
      singulars
      1. POEclipse (Kepler) Workspace acting weird (type hierarchy, searching for references not working)
      1. USDerStrom8
    2. COI do have a feeling it's probably something in the .metadata, but as I've said in the question, clearing out the .metadata\.plugins\org.eclipse.jdt.core folder (clearing out the indexes) does not work :-(
      singulars
      1. POEclipse (Kepler) Workspace acting weird (type hierarchy, searching for references not working)
      1. USbknopper
    3. COI'm sorry, I must not have seen that part
      singulars
      1. POEclipse (Kepler) Workspace acting weird (type hierarchy, searching for references not working)
      1. USDerStrom8
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload