Being an old NetBeans lover I’ve almost started feeling depressed second time for the last 10 days. My first disappointment was Spring Roo, which is going to be supported only by Eclipse – NetBeans and IntelliJ users are outboard.
Basically, the problem is that Spring Roo is heavily based on AspectJ, which is not fully supported by the both platforms. Roo followers may argue that the best IDE for Roo is the console app (with is really really good and well-developed by SpringSource team), but as a typical enterprise Java developer, I’m tied to Windows platform (which is a common corporate standard), so in the most cases I prefer to leverage the advantages of modern graphical IDEs.
The second disappointmend could have become Project Lombok (that was highlighted on the last JavaPosse roundup). Founded by two enthusiasts, Project Lombok was integrated only with Eclipse until recently (though project contributors were actively looking for support in NetBeans and IntelliJ communities to help with making pligins for these IDEs). But in the last beta version, rich support for NetBeans was added.
So what’s the idea behind Lombok. Simply putting lombok.jar to your classpath you can remove a lot of boilerplate code from your old Java classes. For example, @Data annotation allows you to make a kind of Scala’s case class of your bean.
(more…)
