Software is too expensive to build cheaply...

Filippo Diotalevi wrote about a wishlist for a better JUnit, and he mentioned Cedric's pet idea of using annotations to identify test cases.

Weiqi Gao complains that combo boxes are lame because you can't type in them. He gives a good example of the state abbrevation MO for Missouri; in a typical drop-down list of US states, you need to go through seven M's to get there.

Seeing all the comments today about using annotations to declare test cases reminded me that I never got around to writing about what I didn't like about TestNG

Euxx is worried that there will be stuff lost in the head-long plunge into annotations. Annotations won't be the death of XDoclet, nor for that matter will they be the death of deployment descriptions.

It's simple, highly flexible, and extremely versatile.

After having to work out how to do this again, I thought I'd give a step-by-step guide to creating an Eclipse Update site, populated by existing plugins. For this example, I'll create an update site for the Weblogic Eclipse plugin.

Yep, Ant 1.6.2 has been released. And the forkmode option for JUnit is there!. I'm really happy.

Little warning for anyone else who stumbles across this problem: the stylesheet used for <junitreport> in Ant 1.6.2 does not work with Xalan 2.2. Unfortunately, this is the version that's bundled inside the rt.jar in Java 1.4.1.

This is a cautionary tale of US-only JREs and non-US countries, such as The Lucky Country I call home.