Bug 192856 - [compiler] No package information for "Type mismatch" compiler error.
Summary: [compiler] No package information for "Type mismatch" compiler error.
Status: RESOLVED DUPLICATE of bug 241841
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows XP
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: Philipe Mulet CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-06-15 08:38 EDT by Marcin Kowalski CLA
Modified: 2008-08-25 07:17 EDT (History)
1 user (show)

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 Marcin Kowalski CLA 2007-06-15 08:38:05 EDT 
Build ID: M20070212-1330

Steps To Reproduce:
1. Create two classes with identical names but in different packages.
2. Write a method that returns your class no.1
3. Declare a variable of type no.2 and try to assign no.1 with a method call. What you will get in error description is "Type mismatch: cannot convert from MyTypeName to MyTypeName"


More information:
This is a minor issue, but annoying. Because only one type needs to be imported, there is no need to use full package name with conflicting classes and the resulting error message is a little bit lacking information.
Comment 1 Philipe Mulet CLA 2007-10-12 09:52:19 EDT 
We did de-qualify our type names in error messages to improve readability; in such (rare) cases, I agree this doesn't help.
Comment 2 Nicholas Sherlock CLA 2007-12-04 20:04:25 EST 
I suggest that Eclipse should qualify the names in the error message if and only if the two names it is about to present are currently identical.
Comment 3 Philipe Mulet CLA 2008-08-25 07:17:30 EDT 

*** This bug has been marked as a duplicate of bug 241841 ***