Bug 28666 - Unclear error message for invalid output folder
Summary: Unclear error message for invalid output folder
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: 2.1 M5   Edit
Assignee: Jerome Lanneluc CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 30470 (view as bug list)
Depends on:
Blocks:
 
Reported: 2002-12-19 07:10 EST by Jerome Lanneluc CLA
Modified: 2003-02-07 11:48 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jerome Lanneluc CLA 2002-12-19 07:10:28 EST
Build 20021218

In the build path property of project P1, if you enter a path to another 
project (e.g. P2/bin), you get an error message that just says 'P2/bin'.
Comment 1 Jerome Lanneluc CLA 2002-12-19 07:11:37 EST
BuildPathsBlock.updateBuildPathStatus() should use IJavaModelStatus.getMessage
() instead of IJavaModelStatus.getString().
Comment 2 Martin Aeschlimann CLA 2003-01-07 03:37:13 EST
Note that I recently changed from IJavaModelStatus.getMessage()
to IJavaModelStatus.getString() because getMessage gives an unspecific message 
like 'Name collision.' I just checked in 200212, it still seems to be the case.

I agree that that getMessage() should be used, and changed back. (> 20030107)
Can you please make sure that getMessage is at least as good getString()?
Maybe to get rid of the confusion getMessage could return the same as getString 
(deprecate getString?)
Comment 3 Philipe Mulet CLA 2003-01-07 08:19:56 EST
Name collision sounds counter intuitive, we should improve this message anyway.
Suggestion for matching #getString behavior is interesting too.
Comment 4 Jerome Lanneluc CLA 2003-01-24 08:55:02 EST
Deprecated getString() and changed getMessage() to use the string in the case 
of NAME_COLLISION.

Updated ClasspathTests.testDuplicateEntries() to reflect this change.
Comment 5 Jerome Lanneluc CLA 2003-01-29 10:28:36 EST
*** Bug 30470 has been marked as a duplicate of this bug. ***
Comment 6 David Audel CLA 2003-02-07 11:48:10 EST
Verified.