Bug 119707 - [open type] problem resolvoing a type from classpath folder
Summary: [open type] problem resolvoing a type from classpath folder
Status: RESOLVED INVALID
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on: 148380
Blocks:
  Show dependency tree
 
Reported: 2005-12-07 14:06 EST by John Kaplan CLA
Modified: 2009-08-30 02:06 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description John Kaplan CLA 2005-12-07 14:06:14 EST
Steps to reproduce:

1 Select File > New > Class
2 Type in some class name
3 Select Superclass: Browse... button
4 Type/pick a generic class from the list.
Expected - eclipse uses the generic superclass correctly and allows you to pick it.
Actual - Error alert is displayed, saying: "Could not uniquely map the type name to a type. Path is ..." and when you click the box away you are dumped back into the New Class Wizard.

Workaround manually enter the fully qualified class name into the New Class Wizard box (including angle brackets and type name), and eclipse reacts more-or-less the way you would expect.
Comment 1 Martin Aeschlimann CLA 2005-12-09 09:04:45 EST
This seems to work for me.
The type selection dialog shows all types without type parameters. When selecting one, the type is also inserted without. We allow toy to add the brackets.

Can you provide a reproducable example? Which type gave you that error message?
Anything in the log?
Comment 2 John Kaplan CLA 2005-12-12 14:47:59 EST
The version I am on is 3.2M3.

One part of the repro case I should have mentioned is that the parent class/interface you are trying to extend is from a different project.

So steps to reproduce are:
Create a project and create a generic class or interface in that project.
Create another project and import the superclass/interface definitions by using the Libaries Tab, Add Class Folder... option.

Then follow the previously defined steps in the new project. This consistently reproduces every time for me with both extending a parent generic interface, and subclassing a parent generic class. The parent class does appear in the pick list, but when you pick it, you get the error as previously described.

If the generic superclass and subclass are in the same project, it works fine, as you describe.
Comment 3 Martin Aeschlimann CLA 2006-06-23 09:06:36 EDT
Problem is that we fail to handle types from class folders in other projects:

The path is 'Project1/cf' and JavaCore.create results in a type that does not exist. We finally need support from jdt.core here. I filed request 148380.
Comment 4 Denis Roy CLA 2009-08-30 02:06:00 EDT
As of now 'LATER' and 'REMIND' resolutions are no longer supported.
Please reopen this bug if it is still valid for you.