I’m known as an enemy for Eclipse, ‘coz I hate it. And I’ll stick to be like this till they change some major usability issues. And one more final side-note; yes Eclipse RCP sucks!

And I still don’t see any reason why everybody still tend to use it :S I guess there is only one good reason. It’s free. When you’re a student, you can’t afford expensive tools. And at the time there was no Netbeans to compete with it. So people who are manager or decision maker in the market right now have generally been through such a career path :) So basically they don’t even know other development tools, or they don’t wanna learn a new tool. And on top of this, if you’re also cheap, here is final result: Eclipse is free :P

It’s long discussion. Personally I hate 3 things in Java world: Eclipse, IBM and JVM architecture. You could comment how they’re great, but you can’t change my mind about these 3 :) I’ve seen enough about them. Anyways :) Let’s get back to tip :)

If you’re having trouble with a legacy unit test, and if your build is failing, sometimes you might want to exclude those failing tests from build path. It is actually pretty easy. All you need to do is right click to failing file in the package explorer and then select the build path menu item. After that menu pops up, you’ll quickly notice that there is an exclude menu item there. Just click it :) Pretty easy right?

So far it is so easy. The reason I’m talking about this option is, it is applicable for all validation errors including XML, Velocity, Groovy, and so on..

That’s it, enjoy.. uhmm.. Sorry I actually meant continue to your war with Eclipse!

<

p>Ah! One last thing which IDE do I personally use? Of course IntelliJ IDEA :)