Bug 98909 - [Navigator] Moving Ant-file crashes Eclipse
Summary: [Navigator] Moving Ant-file crashes Eclipse
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Francis Upton IV CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-06-08 07:20 EDT by Gregor Rosenauer CLA
Modified: 2019-09-06 16:11 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gregor Rosenauer CLA 2005-06-08 07:20:29 EDT
I am running Eclipse 3.1rc1.
When I tried to move an Ant-build-file to another location inside the same
project by invoking "Move" in the Navigator, Eclipse started the process but
something strange happened in the middle of the Move-process:
The buildfile was reverted (!) to the last state (the editor was updated in the
background), and then nothing happened, leaving the "Move"-window in a stale
state, not accepting "Cancel"-requests or anything.
After some minutes passed, I decided it was time to say goodbye to the process.
Comment 1 Darin Swanson CLA 2005-06-08 10:21:55 EDT
Was there any information in the log file: Window>Show View>Other>PDE 
Runtime>Error Log
Comment 2 Gregor Rosenauer CLA 2005-06-08 11:28:06 EDT
Sorry, there was no output in the log. Also, Eclipse did not actively "crash",
but I had to kill it since it stopped responding.
The log however shows that Eclipse detected a workspace crash:

Message: "A workspace crash was detected. The previous session did not exit
normally."

An exception stack trace is not available.
Comment 3 Eclipse Webmaster CLA 2019-09-06 16:11:55 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.