DDevelopment & Design

GWT Designer for Eclipse 3.6 can cause project compile freeze

Lately I installed GWT Designer for Eclipse Helios (3.6). I wanted to check it’s features. They aren’t so cool I’ve expected but that’s other story. The problem was that suddenly my main GWT enabled project began to freeze during compilation.  The…Lately I installed GWT Designer for Eclipse Helios (3.6). I wanted to check it’s features. They aren’t so cool I’ve expected but that’s other story. The problem was that suddenly my main GWT enabled project began to freeze during compilation.  The…

Lately I installed GWT Designer for Eclipse Helios (3.6). I wanted to check it’s features. They aren’t so cool I’ve expected but that’s other story. The problem was that suddenly my main GWT enabled project began to freeze during compilation.  The project is maven enabled also.

So it freezed in about half of compilation. All other features of Eclipse worked well. Restarting Eclipse and Windows didn’t help anyway.
After about an hour of investigating I’ve found that GWT Designer caused this. After removing it all came back to order.

Ofcourse I suspect that something is wrong with my Eclipse for example I have too many bizzarre plugins installed but if I could have such problems you could have them too. So be warned :-)

— Previous article

Spring Security by example: securing methods

Next article —

Testing ServiceMix 4.3 services with PaxExam

You May Also Like
DDevelopment & Design

Context menu or Action buttons ?

Recently I was drawn into one of those UI "religious" disputes that has no easy answers and usually both sides are right. One of our web developers was trying out new web tech (with pretty rich widget library) and started to question himself about some basic usability decisions. The low level problem in this case is usually brought to "which widget should I use ?". I'm not fond of bringing the usability problems to questions: Should I use Tabs over Menu ? Or should I use Context menu instead of buttons panel ? But sometimes if time is crucial factor and other usability levels are by default not addressed at all - better developer that asks those basic questions than developer that do not question himself at all.