Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 311091 - [LinkedResources] Misleading message when enabling linked resources
Summary: [LinkedResources] Misleading message when enabling linked resources
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: IDE (show other bugs)
Version: 3.6   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Serge Beauchamp CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-29 14:55 EDT by John Arthorne CLA
Modified: 2021-09-30 14:00 EDT (History)
0 users

See Also:


Attachments
Fix v01 (4.41 KB, patch)
2010-04-29 15:23 EDT, John Arthorne CLA
no flags Details | Diff
Fix v01 new patch (3.99 KB, patch)
2010-05-06 14:47 EDT, John Arthorne CLA
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description John Arthorne CLA 2010-04-29 14:55:44 EDT
Build: I20100428-0100

1) Open the "linked resources" preference page.
2) Disable linked resources (first checkbox)
3) Enable linked resources.

You get the following warning message, "You have enabled a feature which may give rise to incompatibilities if projects are shared by users of different versions of the workbench.  Please consult the documentation for further details."

This message comes from the first release of linked resources where you would have compatibility problems if you shared a workspace between Eclipse 2.0 and 2.1. This message should just be removed now. Nobody is sharing workspaces between Eclipse 3.6 and 2.0. For everyone else this message is just confusing and misleading.
Comment 1 John Arthorne CLA 2010-04-29 15:23:31 EDT
Created attachment 166556 [details]
Fix v01

I happened to be looking in this code so I wrote a patch.
Comment 2 John Arthorne CLA 2010-05-06 14:47:52 EDT
Created attachment 167366 [details]
Fix v01 new patch

The previous patch became stale. Here is a new patch with the same fix.
Comment 3 Serge Beauchamp CLA 2010-05-10 07:51:24 EDT
That sounds good to me.

Also something that pops my mind, is whether the checkbox should be displayed at all, and linked resources simply not being always enabled.

Besides the fact that I bet a lot of thing would cause problems (besides linked resources) moving a project that was created on 3.6 to 2.0, if the user doesn't create linked resources, then there's no incompatibility.

The same applies for other features such as the resource filters - if the user imports a 3.6 project that contains resource filters in 3.5, they will be silently ignored.

For me, the ideal solution would be that core.resources would version the .project file, so that when we import projects in Eclipse, we can know before hand if it was created with a later Eclipse version, and that some elements are incompatible, and inform the user.

Right now, if we do that (import a 3.6 project that has virtual folders, and resource filters), we get an error dialog that says "Creation Problems", with a cryptic (for the user) description.
Comment 4 Eclipse Webmaster CLA 2019-09-06 16:05:54 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.
Comment 5 Eclipse Genie CLA 2021-09-30 14:00:03 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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.

--
The automated Eclipse Genie.