Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 313975

Summary:	The Core Resources API should support adding 'permanent' properties to the .project file
Product:	[Eclipse Project] Platform	Reporter:	Serge Beauchamp <serge>
Component:	Resources	Assignee:	Platform-Resources-Inbox <platform-resources-inbox>
Status:	RESOLVED INVALID	QA Contact:
Severity:	normal
Priority:	P3	CC:	john.arthorne, Szymon.Brandys
Version:	3.6
Target Milestone:	---
Hardware:	PC
OS:	All
Whiteboard:

Description Serge Beauchamp

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

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

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

2010-05-25 13:54:56 EDT

Ah great, thanks, I didn't realize that.