Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 313975 - The Core Resources API should support adding 'permanent' properties to the .project file
Summary: The Core Resources API should support adding 'permanent' properties to the .p...
Status: RESOLVED INVALID
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Resources (show other bugs)
Version: 3.6   Edit
Hardware: PC All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Resources-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-21 15:59 EDT by Serge Beauchamp CLA
Modified: 2010-05-25 13:54 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 Serge Beauchamp CLA 2010-05-21 15:59:40 EDT 
Right now, we have:

- session properties (for a session only)
- persistant properties (within a single workspace only)

But not any 'permanent' properties that persist across workspace, when a project is imported in a different workspace.

We have the need for such API where simple client defined properties are stored in the .project file.

Is there a reason why this wasn't implemented, or just there wasn't the requirement yet?
Comment 1 John Arthorne CLA 2010-05-21 22:40:04 EDT 
Yes, this is what the ProjectScope is for. The advantage of using the preference API here is that it allows cascaded property lookup, where we look in project scope, then instance scope, configuration scope, etc. It also has slightly richer API for getting/putting primitive types rather than just String.
Comment 2 Szymon Brandys CLA 2010-05-25 11:29:37 EDT 
Serge, if the ProjectScope is fine for you, I would mark the bug INVALID.
Comment 3 Serge Beauchamp CLA 2010-05-25 13:54:56 EDT 
Ah great, thanks, I didn't realize that.