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

Bug 206343

Summary:	[Preferences] Project scoped preferences re-write comment even if preferences do not change
Product:	[Eclipse Project] Platform	Reporter:	Mark Melvin <mark.melvin>
Component:	UI	Assignee:	Platform UI Triaged <platform-ui-triaged>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	angvoz.dev, dj.houghton, gerhard.schaber, Kevin_McGuire, martin.gutschelhofer, mschorn.eclipse
Version:	3.3	Keywords:	helpwanted
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:	stalebug

Description Mark Melvin

2007-10-15 12:04:07 EDT

Build ID: I20070625-1500

Steps To Reproduce:
I have a settings file that uses project scoped preferences to store various build settings.  These are checked into CVS with the project.  When a user checks out a new project, my builder does a scrub of the preferences and flushes the node, but even if no preferences change the Eclipse preference infrastructure re-writes the comment at the top of the file, essentially causing a resource change (and triggering a build) when none is required.  It also is a nuisance because the file is marked as changed and usually is checked back into CVS unwittingly by the user - when the only difference is the comment at the top of the file.

Would it be possible to avoid touching the file if none of the preferences have changed?  It is pretty easy to walk the nodes and figure this out.  

If that is not doable, is it possible to make the comment optional - perhaps allowing the user to configure whether they want a timestamp comment in the file when they create the scoped preferences?

Comment 1 Kevin McGuire

2007-10-16 22:02:33 EDT

Also a problem for pessimistic repositories like ClearCase since file will be immediately checked out/locked.

Comment 2 Markus Schorn

2008-07-02 03:33:09 EDT

Also a problem for CDT: When importing a project, the project preferences are always (internally) marked as dirty. So (as a workaround) I need to carefully avoid flushing the project preferences.

Comment 3 Susan McCourt

2009-07-09 19:29:09 EDT

As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009

Comment 4 Lars Vogel

2019-11-27 07:12:34 EST

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.

If the bug is still relevant, please remove the stalebug whiteboard tag.