Bug 185603 - Slash missing in path reported in build error message
Summary: Slash missing in path reported in build error message
Status: CLOSED WORKSFORME
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.0.2   Edit
Hardware: PC Windows XP
: P3 trivial (vote)
Target Milestone: 3.3 RC4   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-05-04 15:50 EDT by Laszlo Benedek CLA
Modified: 2007-06-25 13:32 EDT (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 Laszlo Benedek CLA 2007-05-04 15:50:32 EDT 
Build ID: 200609251014 (Eclipse 3.0.2.5 used as base in RAD 6.0)

Steps To Reproduce:
1.Create a Java project and add an external jar to its classpath.
2.Delete the jar then rebuild the Java project.
3.The validation message that shows up in the Problems view is missing a slash after the drive letter.

I haven't tried it with the with Eclipse 3.3, but the steps should be the same.




More information:
Comment 1 Jerome Lanneluc CLA 2007-05-07 05:26:10 EDT 
I tried your steps with eclipse 3.0.2 and Eclipse 3.3 M7 and I could not reproduce. Do you have more details ?

Also the last official Eclipse 3.0.2 build is 200503110845, so I'm not sure what 200609251014  corresponds to.
Comment 2 Jerome Lanneluc CLA 2007-05-07 10:34:53 EDT 
Exact steps are:
1. New workspace
2. Create a Java project 'P'
3. Add an external jar (e.g. D:\temp\test.jar) on the build path of P
4. Go to the file system and delete the external jar
5. Select P
6. File > Refresh
Observe: The Problem view shows "Project P is missing required library: 'D:temp/test.jar'"
Comment 3 Jerome Lanneluc CLA 2007-05-07 10:36:30 EDT 
The problem doesn't happen with 3.3 M7. The Problems view shows: "Project 'P' is missing required library: 'D:\temp\test.jar'"
Comment 4 Jerome Lanneluc CLA 2007-06-22 09:01:40 EDT 
Works now using 3.3RC4.
Comment 5 Laszlo Benedek CLA 2007-06-22 18:01:39 EDT 
I can close the defect if there are no plans for a fix in 3.0.2
Comment 6 Laszlo Benedek CLA 2007-06-25 13:32:26 EDT 
Closing the defect since it has been fixed in Eclipse 3.3 and no fix is required for 3.0.2