Clover 1.2

In amongst GPRS based mobile systems I’ve been developing at Cortex, I’ve also been working a little bit on Clover 1.2 in recent weeks. This has now been released. For me, an Ant user, the use of filesets and hence the ability to use selectors give lots of ways to slice and dice coverage reports. Funnily enough it’s my first real use of selectors. They are pretty cool. Of course, anything can be abused – be careful not to turn this into a blame train …

The big addition for 1.2 is an IDEA plugin. Actually I don’t use an IDE for my development work. Should I be? I have in the past right back to Turbo-C but never found them as flexible a general purpose editor. I now use jEdit which works the same on both my major platforms, you can find out more at Certainly, the cover-lover keeps hinting that I should be using IDEA. Since he used to be an emacs fan, his conversion is all the more startling.

The arguments for an IDE are usually about productivity from all the time saving gadgets that come with it. They certainly look cool in IDEA. I wonder, however, if the improvements in productivity at the micro level translate to anything meaningful at the macro level.

2 Replies to “Clover 1.2”

  1. My comments regarding “productivity at the micro level translate to anything meaningful at the macro level” revolve around the fact a good IDE (say, IDEA) let’s you do the same thing you normally do, just quick, and without getting in your way.

    When trying to grok/debug code, I often want to “drill down” to the implementation of a method. In Emacs, I can do a “grep find”. This takes a little while, and often results in false positives. In IDEA/Eclipse, I just hit the “goto implementation” hotkey.

    In combiniation with hotkeys for setting bookmarks and a good “back” button, I can zoom around java code and grok what is going on in a very short amount of time. This alone saves me *so much time*.

    I like IDEA because of many of its *editing* abilities, but even more, I love it’s *viewing/browsing* abilities.

  2. I use jEdit for my XML editing, but IDEA for java projects. Try it. Once you get used to it, it is incredibly productive.

    Embrace refactoring, utterly integrated browsing and type sensitive property/method completion. You’ll love it.

Comments are closed.