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

Bug 345455

Summary:	[IDE] Copy(Ctrl-C) & Pasting(Ctr-V) from Windows file system into Eclipse does not preserve original source files "Last Modified" time.
Product:	[Eclipse Project] Platform	Reporter:	Fred Bickford IV <fabickfo>
Component:	IDE	Assignee:	Platform UI Triaged <platform-ui-triaged>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	prakash
Version:	3.7
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:	stalebug

Description Fred Bickford IV

2011-05-11 11:50:58 EDT

Build Identifier: Build id: M20100909-0800

Copying and pasting a file from outside the SDK in from a Windows dialog such as Explorer etc does not preserve last modified time. The files last modified time will be set to current(same as if a user created the file>new). This is confirmed either by the Eclipse properties page for that file or by looking at the file properties via Windows Explorer in the workspace directly.

I have reproduced this on 3.4.2 as well both on Windows 2003 and Windows XP SP3
Searched defects I saw a defect related to "Last Modified" time, yet the use case is slightly different.

I searched for existing defects and found none. https://bugs.eclipse.org/bugs/show_bug.cgi?id=340201 has a similar behavior, yet the use case was different, so I decided to submit the defect.

Reproducible: Always

Steps to Reproduce:
1.Create a file in Windows Explorer , open properties and note "Last Modified" time.
2.Create a Simple project in Eclipse and note Workspace location
3.Copy and past file from Step 1 into directory in Step 2(Via Windows Explorer), observe "last Modified" time IS preserved.
4.Delete File from Step 3 from workspace
5. Refresh Eclipse IDE and confirm it was removed.
6.Copy and past file from Step 1 into directory in Step 2(via Eclipse), observe "last Modified" time IS NOT preserved.

Comment 1 Lars Vogel

2019-11-14 02:21:06 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.