Please ignore ... this was one of the builds I triggered last night when I was setting up the new Hudson jobs. (the job finished 15hrs ago and only now this email is sent ... strange ... Hudson overload?)
This issue was again due to an old jsk-policy.jar that was left behind in the Hudson node's JVM extension directory. I added the uninstall-policy target to the build job to clean this up gradually (since there are multiple nodes, and the build job could have been run on any of these nodes before, this will probably happen multiple times, but the next times will be intercepted by the uninstall-policy call). As far as I can see, the ubuntu1 and solaris1 nodes are clean now, we will have to wait until Hudson selects ubuntu2 to build on before that one is cleaned too. After that, we can safely remove the uninstall-policy target from the build jobs again.
