A couple of days ago the new Ubuntu was released; version 11.10 named Oreiric Ocelot. Of course, I jumped on it and added it to my workstation and server.
The VMWare machine for Mac OS, Fusion, has released a new version, v4.
The server running this blog (and other sites and other software) is a repurposed desktop.
In my more recent experimentations I'm finding that my first-pass, hasty testing of JDK7 on old projects is not as much of a failure as I'd thought it was. The problem lies not with my project, the IDE, the new JDK, or the old libraries, but with the code-coverage tool I use to make sure I'm not missing tests on my code.
Not Eclipse so much, as the experience of using it. I guess they kind of go hand-in-hand, but I'm not ready to blame Indigo.
JDK7 doesn't seem to play nice with Spring 3.0.5 out of the box.
I've run into this from time-to-time, and usually not had to bother with it as authentication usually happens within an application, but on this project I'm trying to enforce the SSO a bit more, so I needed to get Apache to pass Tomcat the user that it has used to authenticate. Should you need to do the same, here's the two-word solution.