Bug 104996

Description Martin Olsson 2005-07-25 08:30:22 EDT

So I'm just editing my plugin.xml and all is well. I'm pressing CTRL-S every 
now and then as I always do (for no sane reason). Sometimes I save even though 
an extension point or actionSet-action/menu etc are not completely filled in. 
In the middle of it all I take a look at the raw version of plugin.xml and now 
it won't let me even use the GUI editor until I fixed all the errors in the raw 
version of the file... and when I look at it a little bit more carefully I find 
lots of attributes and tags called PluginElementNode@df3384 etc.

In the middle of this I start to panic a little bit so I just press the CTRL-Z 
keys and keep them pressed while the editors undos a ton of stuff at lightning 
speed. Then all the suddenly the whole plugin.xml GUI thing crashes on me and 
says ABNORMAL WORKBENCH CONDITION. It says some exception occurred but it gives 
no clue as to what exception and certainly no stacktrace (not even in 
details?!). This is how it looked:

http://mnemo.minimum.se/eclipse_crashes/undo_crash_two.png

(it should also be obvious from this image that
I got some serious MSPaint skills :-D)

Also try to create an actionSet empty the boxes for id and label, then press 
save. Then it says only "Save Fail:null" and nothing else.. what kind of weird 
error message is that? Why can't it just save a raw file with id="" like any 
sane person would expect?

In general, in all parts of Eclipse error messages should say what exception 
occurred. And in details there should always be a proper stacktrace. Why are 
you guys so sloppy with this? Of course, sitting idle myself I cannot expect 
someone else to do the work but maybe atleast new code would try to display 
better error messages? As it stands today I don't even know where to begin 
searching for these bugs.