Bug 182722 - [LinkedResources] Must specify URI shcheme for linked
Summary: [LinkedResources] Must specify URI shcheme for linked
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.2.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 198091
Blocks:
  Show dependency tree
 
Reported: 2007-04-17 06:22 EDT by gilles fenet-garde CLA
Modified: 2019-09-06 16:18 EDT (History)
2 users (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 gilles fenet-garde CLA 2007-04-17 06:22:02 EDT 
Build ID: M20060921-0945

Steps To Reproduce:
1.Create root directory testBuggEclipse and new workspace inside it (Wskp3.2)
2.Copy or create java source in testBuggEclipse/MyDevDir/src/java
For test we provide one file simplepackage.SimpleClass.java
3.choose Menu Window/Preferences/General/Workspace/Linked Resource
4. Choose New with Name = rootDev
5. Click on Folder and search the root directory testBuggEclipse and click Ok
6. Do menu File/New/Project/JavaProject and Next
7. give one name for project MyProject
8. Choose Create project from existing source
9. Type rootDev/MyDevDir
10. Click Next : => Message box with this informations :
An erreor occurred while creating project.
Reason  : Must specify a URI scheme:rootDev/MyDevDir
here is the bugg




More information:
The sames operation with a version Eclipse 3.1.0 build id I20050627-1435 dont' cause the bug and run likely .
We try the likely sample on Linux after Windows XP and the bugg is present also.
English it's not my favorite language, you see ?
Comment 1 Boris Bokowski CLA 2009-11-26 16:23:34 EST 
Oleg is now responsible for watching bugs in the [LinkedResources] component area.
Comment 2 Eclipse Webmaster CLA 2019-09-06 16:18:44 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.