Bug 195693 - Add option to control Archive attribute on derived resources (Windows)
Summary: Add option to control Archive attribute on derived resources (Windows)
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Resources (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows All
: P5 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-Resources-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-07-06 15:07 EDT by TGE Mising name CLA
Modified: 2019-09-06 15:33 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description TGE Mising name CLA 2007-07-06 15:07:30 EDT
This probably a dual IResource + Workbench change.

I would like a Workbench preference to control the Windows Archive bit on all derived resources. The default is to mark it as dirty (set), I would like to leave it clear.  The preference should probably allow: Default behavior, always set, always clear.  I could see where a developer workspace might want always clear, but a build workspace would want always set.

I am not sure if the *nix flavors have a similar attribute or not.

This would save a LOT of space on backup systems without having to create custom filters, etc.  Standard windows practice is that the archive bit is set during file modifications, and cleared during backups.

I would be curious as to the performance impact of this change on large workspaces.  Default behavior should have no impact.

If this is implemented, consider implementing in such a way to allow other settings to be propagated by the same methods. (System, Hidden)

Thanks.
Comment 1 Eclipse Webmaster CLA 2019-09-06 15:33:02 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.