livescribe released Version 2.0 of Livescribe Desktop for Mac

Today I found the announcement that livescribe released the 2.0 version of the Livescribe Desktop (LD) for Mac.

I downloaded and installed the new version and I’m really happy to see that I’m now able to print my own Notebooks on the Mac. Now I can get rid of the Windows version that I used for this reason only. That’s really great! Thanks for this long missing feature.
The other big change is the integration of the Livescribe Store into LD. I’m really curious what I’m about to find there once it’s up and running. I hope to find some Goodies there to pimp up my Pen. Perhaps I get an Application which will help my Pen to write alone. Without any intervention from my end. That would be awesome. ;-)

Never use System.exit(1) in a groovy script

I wrote a small groovy script to to do some maintenance tasks on my machine. At some point the logic got a little bit more complicated and I decided to write some simple testcases. I executed the testscript and was really surprised about the output: the test should fail but it didn‘t! Now I tried to nail it down with limiting the scope to a very simple method call but the result was exactly the same. Hm, I thought it must have something todo with log4j that I used to write everything into the logfile. So I removed the log4j dependency and started the tests again. To my surprise the result didn‘t change at all. There was no output from junit on the console. I started to look a little bit closer at the class and walked through the constructor call to the method that I called during my test. Bang! There is was! In the constructor I checked for the existence of a certain resource (in this case a mounted volume). If the volume wasn‘t mounted I terminated the script with System.exit(1). I guess this was a really bad idea. Now I changed it to throw new RuntimeException(‘Volume not mounted‘) and everything is fine again.
Lesson learned: Never call System.exit(1) in constructor calls!

Clean Code Developer Plugin for Eclipse

Ich werde mir ein Plugin für Eclipse programmieren um die Prinzipien, Regeln und Praktiken eines Clean Code Developers immer vor Augen zu haben. Ich habe bis jetzt noch nichts passendes für Eclipse gefunden um einen Einsteiger in die Materie gezielt zu unterstützen. Also werde ich mich an die Arbeit machen um das Plugin zu basteln.
Was soll das Plugin machen? Nun, es soll den aktuellen CCD-Grad und die damit verbundenen Prinzipien, Regeln und Praktiken zusammenfassend darstellen. Am besten wäre es, diese als Links auf die Clean Code Developer Website verweisen zu lassen. Dort kann dann die genaue und erweiterte Erklärung zu den einzelnen Punkten nachgelesen werden bis sie in "Fleisch und Blut" übergegangen sind.
Meinungen?