Bug 8125 - 'Could not uniquely map the type name' message opening type
Summary: 'Could not uniquely map the type name' message opening type
Status: RESOLVED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 2000
: P1 normal (vote)
Target Milestone: 2.0 M3   Edit
Assignee: Jerome Lanneluc CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-01-23 10:07 EST by Jerome Lanneluc CLA
Modified: 2002-01-23 12:24 EST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jerome Lanneluc CLA 2002-01-23 10:07:20 EST 
Build 20020122

1. Create 2 java projects: JUnit1 and JUnit2
2. In each project, add junit.jar and add it to each project's buildpath
3. Add third java project test with both JUnit1 and JUnit2 on its buildpath
4. Delete JUnit2
5. Workbench->Open Type
6. Select AssertionFailedError and press OK
Observe: You get a message dialog saying: 'Could not uniquely map the type name'
Comment 1 Jerome Lanneluc CLA 2002-01-23 10:10:16 EST 
PackageFragmentRoot.exists() returns true for root A/Junit1/junit.jar.
Problem is with PackageFragmentRoot.isOnClasspath() that uses isPrefixOf(IPath) 
to compare classpath instead of equals(...).
Comment 2 Philipe Mulet CLA 2002-01-23 11:28:24 EST 
Good find.
Comment 3 Jerome Lanneluc CLA 2002-01-23 12:24:22 EST 
Changed from isPrefixOf(...) to equals(...)