Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 40491 - File Archive Attribute Not Set After File is Modified on Windows 2000
Summary: File Archive Attribute Not Set After File is Modified on Windows 2000
Status: RESOLVED DUPLICATE of bug 28790
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Resources (show other bugs)
Version: 2.1   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Resources-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-07-18 14:17 EDT by Clive CLA
Modified: 2003-07-18 16:11 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 Clive CLA 2003-07-18 14:17:11 EDT
On Windows 2000, whether using the Java or Text editor in Eclipse, after a file
is modified, its archive attribute is not set.  On Windows, anytime a file is
newly created or modified, its archive attribute should be set.  Eclipse does
set the archive attribute when it creates a file, but not after its modified. 
To see this attribute, using Windows explorer, right click on the file and
select Properties. On the General tab, at the bottom, click Advanced. If the
archive attribute is set, the checkbox "File is ready for archiving" should be
checked.
To recreate problem, make sure a file does not have the attribute on (follow
steps above and uncheck the "File is ready for archiving" checkbox, and "OK" all
the way out).  Using Eclipse, edit the file and save.  Check the archive
attribute.  It should still be off.  Now use any other Windows based file
editor, such as Notepad.  Edit and save the file.  Check the archive attribute.
 It should be on.
I use this attribute for backup purposes. Xcopy looks for this attribute to copy
"only modified files", as does other utilities.
I tried using other JDKs, but same result.
Eclipse version: 2.1.0, Build id: 200303272130
JDKs tried on (all Sun): J2SDK 1.4.2, J2SDK 1.4.1_01, JDK 1.3.1_08
Comment 1 John Arthorne CLA 2003-07-18 16:11:02 EDT

*** This bug has been marked as a duplicate of 28790 ***