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

Bug 157593

Summary:	[Import/Export] [IDE] Importing project may yield lots of commits
Product:	[Eclipse Project] Platform	Reporter:	Sven Köhler <sven.koehler>
Component:	IDE	Assignee:	Platform UI Triaged <platform-ui-triaged>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P5	Keywords:	helpwanted
Version:	3.2
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:	stalebug

Description Sven Köhler

2006-09-17 14:22:33 EDT

Hi,

i've just imported a Projekt into my Eclipse 3.2 workspace. The project was in my Eclipse 3.1 workspace. The project had no outgoing changes in Eclipse 3.1. While importing it to 3.2, i have checked the "copy projects to workspace" checkbox.

So the files were copied. And i guess, that the copy-routine doesn't copy the timestamps and other information. The result is:
All files of the project were show as outgoing in the synchronized view.


The copy-routine should be changed to maintain meta-information of the files (like timestamps and such things).

Comment 1 Sven Köhler

2006-09-17 14:26:28 EDT

Oh, maybe it's not a good idea to change the copy-routine. It may be used from in many places. Well, at leats in this case, use a copy routine that preserves the file-times etc.

Comment 2 Michael Valenta

2006-09-27 15:48:14 EDT

I believe the copy is performed by the IDE component. A workaround is to perform a Synchronize on the project. That should reset the dirty bit on the files.

Comment 3 Sven Köhler

2006-09-27 15:55:10 EDT

A synchronize won't do, but running a Team->Update on the project will.

The update-operation will need to transfer lots of data (imagine huge binary files and such ...). Really just a workaround.

Comment 4 Susan McCourt

2009-07-15 12:07:27 EDT

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

Comment 5 Eclipse Webmaster

2019-09-06 15:32:56 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.

Comment 6 Eclipse Genie

2021-12-29 01:10:19 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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.

--
The automated Eclipse Genie.