Bug 166341 - [Workbench] Project specific linked resources definitions
Summary: [Workbench] Project specific linked resources definitions
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: IDE (show other bugs)
Version: 3.2.1   Edit
Hardware: PC Windows XP
: P5 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2006-11-30 08:29 EST by Ewan Chalmers CLA
Modified: 2019-09-06 15:37 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 Ewan Chalmers CLA 2006-11-30 08:29:20 EST 
It would be useful if linked resources (Preferences/General/Linked Resources) could be defined in a project specific way. Currently they are defined globally.

Use case. I have a set of projects per product/release I'm working on, sometimes more than one at at time. For each release, all projects share a common directory (e.g. build_area=c:\build\rel_3.1) containing for example jars built by other projects and a "classes" output folder per project. I define that shared root directory as a linked resource. I set up classpath and build output folder with reference to that linked resource. Very useful feature. But I must remember to change the value of the linked resource whenever I switch to a project in another release. So would be useful to define (or override) the value project specifically. If I could do it per "Working Set" in package explorer, even nicer :)
Comment 1 James Blackburn CLA 2008-09-17 09:04:41 EDT 
This bug appears related to bug 229633 which has patches and active discussion.
Comment 2 Susan McCourt CLA 2009-07-15 12:36:16 EDT 
"As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009"
Comment 3 Eclipse Webmaster CLA 2019-09-06 15:30:13 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 4 Eclipse Webmaster CLA 2019-09-06 15:37:35 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.