Bug 318699

Summary: Open Type does not show certain classes
Product: [Eclipse Project] JDT Reporter: Michael Heß <m_hess>
Component: CoreAssignee: JDT-Core-Inbox <jdt-core-inbox>
Status: VERIFIED INVALID QA Contact:
Severity: normal    
Priority: P3 CC: deepakazad, markus.kell.r, Olivier_Thomann, remy.suen
Version: 3.7   
Target Milestone: 3.7 M1   
Hardware: PC   
OS: Windows XP   
Whiteboard:
Attachments:
Description Flags
log of my workspace after starting helios none

Description Michael Heß CLA 2010-07-02 07:44:18 EDT 
Build Identifier: 20100617-1415

I have a problem with at least three (probably more) source files. They are not found in the Open Type dialog.

I have tried deleting the contents of my .metadata\.plugins\org.eclipse.jdt.core but it does not change anything (apart from the indexer redoing its work).

What I do see in the log, is an exception (see attachment). I am not sure if it is related though, as this exception is already written into the log when my instance is started.

Other (probably) important facts:

The files in question can be found through the Open Resource dialog.

The files ARE part of the build path.

The java editor can work with the classes just fine. Also more complex operations, e.g. the call hierarchy, do work just fine.

The workspace this problem happens in is rather complex, made up of several 20-30 projects with interdependencies.

The problem can also be reproduced in my old Galileo SR1 installation (build ID 20100218-1602).

Reproducible: Always

Steps to Reproduce:
1. Start Eclipse
2. Hit <Ctrl>+<T>
3. Type class name -> nothing appears
Comment 1 Michael Heß CLA 2010-07-02 07:47:14 EDT 
Created attachment 173292 [details]
log of my workspace after starting helios
Comment 2 Deepak Azad CLA 2010-07-02 08:01:53 EDT 
(In reply to comment #0)
> Steps to Reproduce:
> 1. Start Eclipse
> 2. Hit <Ctrl>+<T>
I assume this is a typo and you meant 'Ctrl+Shift+T'? No?

> 3. Type class name -> nothing appears
Comment 3 Markus Keller CLA 2010-07-02 08:46:29 EDT 
Moving to JDT/Core for the exception in comment 1.

Can you try whether other search operations for the affected classes work?
Select the class name and do Search > Declarations > Workspace, or use the Search dialog (Ctrl+H) and search for declarations of the class.

Are these source files special anyhow?
- Are they generated?
- Do they contain multiple type declarations or no type whose name matches the *.java file name?
- Do they contain compile errors?
Comment 4 Michael Heß CLA 2010-07-02 08:52:58 EDT 
(In reply to comment #3)
> - Do they contain multiple type declarations or no type whose name matches the
> *.java file name?

Doooh, stupid me. Yes, they are indeed generated, and more important: the filename does NOT match the classes which are defined in there. If I search for the types defined in there, I can find them. So everything is working correctly. Cannot find a type that simply is not there. Sorry for that, guess it is time to get out of the office and start the weekend. ;-)

From my perspective this can be marked as CLOSED/INVALID. Don't know if you want to keep this bug for the exception? Leaving it as RESOLVED for now.

Thanks for the enlightenment!
Comment 5 Olivier Thomann CLA 2011-01-25 11:18:49 EST 
Verified.