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

Bug 162424

Summary:	refactor class move results in jumbled java file
Product:	[Eclipse Project] JDT	Reporter:	Spencer Stejskal <stejsks>
Component:	UI	Assignee:	JDT-UI-Inbox <jdt-ui-inbox>
Status:	CLOSED WORKSFORME	QA Contact:
Severity:	normal
Priority:	P3
Version:	3.1.2
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Spencer Stejskal

2006-10-26 12:07:27 EDT

i was in the java perspective and i moved a class from one package to another via the refactoring move call.  i got impatient and before the refactoring was done i did a organize inputs call on a different class.  the result was the class that was moved was corrupted.  i lost the source informaton because the output was so garbled.  i got it back from cvs without trouble but if i didnt have source control, god forbid, or had uncommitted changes it could have been disasterous.  in hindsight i realize it was a stupid move to continue working during a refactor but how can someone be expected to wait for literally a second or more for a great tool to finish making their life easier:)

Comment 1 Markus Keller

2006-10-27 09:52:55 EDT

I guess with "organize inputs" you mean "Source > Organize Imports". However, I can't reproduce. The refactoring dialog should be modal, so you should not be able to start another operation while the refactoring is executing.

Could you please try to reproduce and post exact steps?

Comment 2 Spencer Stejskal

2006-10-27 11:01:57 EDT

unfortunatly, or maybe fortunatly, i am also unable to reproduce.  sorry

Comment 3 Markus Keller

2006-10-27 11:10:03 EDT

Closing then, please reopen if this happens again.

Comment 4 Spencer Stejskal

2006-10-27 12:40:32 EDT

ill keep an eye out for it.