Bug 325782

Summary:

Open Type often throws an IllegalArgumentException: Class file name must end with .class

Product:

[Eclipse Project] JDT

Reporter:

joseph.gagnon

Component:

Core

Assignee:

Olivier Thomann <Olivier_Thomann>

Status:

VERIFIED WORKSFORME

QA Contact:

Severity:

normal

Priority:

CC:

daniel_megert, Olivier_Thomann, satyam.kandula, thatnitind

Version:

3.5.2

Target Milestone:

3.7 M2

Hardware:

OS:

Windows XP

Whiteboard:

Attachments:

Description	Flags
Screenshots and stack trace	none
Current Eclipse Configuration	none

Description joseph.gagnon

2010-09-20 14:54:04 EDT

Build Identifier: M20100211-1343

In many instances when I attempt to use the Open Type command (either via the menu or key shortcut), I will get an error for each letter of the type that I type in. In some cases, it will continue to show the types that match what was typed, but in some cases the results shows nothing, preventing me from locating the class. See attachment for stack trace.

Reproducible: Sometimes

Steps to Reproduce:
1. Attempt to open a type by typing Ctrl-Shift-T.
2. Begin typing the name of a class.
3. You may (or may not) get the exception as you type characters.

Comment 1 joseph.gagnon

2010-09-20 14:58:17 EDT

Created attachment 179268 [details]
Screenshots and stack trace

Comment 2 Nitin Dahyabhai

2010-09-20 16:20:02 EDT

Do you have anything that builds on the Java tools installed, such as WTP, Groovy, or AJDT?

Comment 3 Dani Megert

2010-09-21 02:12:38 EDT

We have fixed quite a bunch of these issues in 3.6. Please switch to 3.6.1 and if you see it there too, reopen with steps to reproduce.

Comment 4 joseph.gagnon

2010-09-21 07:45:18 EDT

No, we don't have any of the tools you mention. I'm not sure what other things we DO have that could interfere. I'll attach a document with the current configuration.

Comment 5 joseph.gagnon

2010-09-21 07:46:48 EDT

Created attachment 179302 [details]
Current Eclipse Configuration

Comment 6 Satyam Kandula

2010-09-21 08:05:49 EDT

(In reply to comment #5)
As Dani mentioned, please try 3.6. We have fixed some bugs around it, except bug 309903. You could end up in this bug if you have multiple projects, where one project's class path has a class folder which is a source folder of another project.

Comment 7 Olivier Thomann

2011-01-25 11:20:45 EST

Verified.