Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 330311

Summary:

[navigation] The navigation(ctrl+click) on import declaration occasionally does not work for some imports while it works for other imports.

Product:

[Eclipse Project] JDT

Reporter:

bankak

Component:

Text

Assignee:

JDT-Text-Inbox <jdt-text-inbox>

Status:

RESOLVED WORKSFORME

QA Contact:

Severity:

normal

Priority:

CC:

daniel_megert

Version:

3.7

Keywords:

needinfo

Target Milestone:

---

Hardware:

OS:

Windows 7

Whiteboard:

Attachments:

Description	Flags
The eclipse error log file	none

Description bankak

2010-11-16 02:48:34 EST

Build Identifier: 20100617-1415

My workspace has two large projects about ....
The navigation feature, press cntrl and click on the import declaration to go to the corresponding java class, does not work occasionally for some of the imports while at the same time it works for other imports from the same package.

This was found to occur when compiling project within eclipse.
Ex=
import a.b.C1;  // ctrl + click to go to source, does not work occasionally. 
import a.b.C2;  // works.

Also it did not happen on a server machine with faster processors.

Reproducible: Sometimes

Steps to Reproduce:
1.Take a large project.
2.Compile the project within eclipse.
3.Try to navigate on import declaration.

Comment 1 Dani Megert

2010-11-16 02:55:53 EST

Does F3 work in case where Ctrl+Click fails? Anything in .log?

Sorry, but we can't do anything without steps to reproduce this. A possible problem could be that the build path is not correct but that's just a guess.

Comment 2 Dani Megert

2010-11-22 05:43:20 EST

I cannot reproduce this using 3.7 M3 or newer. If you can reproduce with such a build then either provide more detailed steps (best starting off a new workspace) or attach a workspace that exhibits the problem.

Comment 3 bankak

2010-11-23 01:18:02 EST

(In reply to comment #2)
> I cannot reproduce this using 3.7 M3 or newer. If you can reproduce with such a
> build then either provide more detailed steps (best starting off a new
> workspace) or attach a workspace that exhibits the problem.



Sorry,

I missed to give the project sizes,  The projects take around 200 MB each.

Also, F3 too does not work when the hyperlink does not work.

Since the projects are proprietary, I can not share the workspaces.

Please let me know if there is anything else I should try.

To Note, I have a couple of custom plugins installed in my workspace, could it be related to that. They are showing some "Keybinding conflicts occured" in the error log.

Comment 4 Dani Megert

2010-11-23 02:54:48 EST

> Also, F3 too does not work when the hyperlink does not work.
OK, that means that search is not working, probably due to an indexer problem.

> Please let me know if there is anything else I should try.
- attach the full .log here
- try 3.6.1

> To Note, I have a couple of custom plugins installed in my workspace, could it
> be related to that.
It can but you'd only now after uninstalling them.

Comment 5 bankak

2010-11-23 07:16:16 EST

Created attachment 183660 [details]
The eclipse error log file

Comment 6 bankak

2010-11-23 07:18:42 EST

I have attached the error log file. Please take a look at it.

Comment 7 Dani Megert

2010-11-23 08:32:22 EST

Looking at your log your workspace seems pretty damaged - JDT Core even failing to initialize and there's nothing we can do if we don't get steps or access to your workspace.

I suggest you switch to 3.6.1 and start with a fresh workspace.