Archive for the ‘Coding horrors’ Category.

Final java dev environment

Screen shot of eclipse with a dark color theme while editing jBug

Screen shot of eclipse with a dark color theme while editing jBug

I’ve been going back and forth between IntelliJ’s idea, netbeans and eclipse for java development. I was able lately to setup eclipse with all the features I need, and performs all the compilation function required including pulling maven dependencies and hot deploying jetty’s code on save and the best thing was the ability to edit it’s colors using the CSS provided.

How to do that:

1. Using git clong jBug from
2. Inside there, there’s a directory called “settings” in which there are two files: preferences.epf (which includes the editor settings and color theme) and e4_default_gtk.css and that will set the color and font sizes of the tabs.
3. Copy the css file over your eclipse/plugins/org.eclipse.platform_4.2.1.v201209141800/css/e4_default_gtk.css

For plugins, using the market place add the following:

1. egit (to integrate with git)
2. Run-jetty-run, will use in-place deployment with jetty and will close and open the handlers and contexts if you change any of your classes or their dependencies (excellent work)
3. m2e for maven
4. Eclipse color theme. In case you wanted to change the theme edit the wombatcss.xml then import it.

Since eclipse is not a limited edition as idea, you will be able to edit jsp and other files that you won’t be able to edit in idea. It is also much more efficient in terms of memory usage than netbeans and does not block or stop erratically like netbeans as well.

Back to netbeans again after intelliJ misrepresenting compilation

So IntelliJ says it compiled successfully a project. However, when I execute maven jetty plugin to run a small web project, I end up with jars not being found. So what does it exactly mean when IntelliJ says compile successfully ? It seems that it just compiles them, and it really does not make any difference whether you compile or Make the project both cases will result in missing jars if you run the project using maven jetty plugin.

There’s lots of crap in netbeans however it seems to be the only edit that does what it says it’s going to do in terms of maven compilation. It sill suffers from some issue like for example you won’t be able to disable tests if you compile with dependencies.

For the time being I have to accept the flaring white colors of netbeans until one day I can figure out a more consistent way of configuring it.