I've released XOM 1.2.4, my free-as-in-speech (LGPL) Java library for processing XML. The major change in this release is a hopefully user-transparent one-button release process. This still needs some work though. The Ant target to tag the release in CVS is broken (I'd appreciate it if anybody coudl figure that out). Furthermore, it's still hooked up backwards. The release is bundled and deployed from my local hard drive, and then tagged in CVS. What should happen is that first I tag the release as an independent target. Then the deploy target checks out a tagged version from CVS and uploads that. This would make sure that what's deployed macthes what's in the repository. It would also make it a little easier to build older versions when someone needs one. As is, CVS is just sort of off to the side of the deployment chain rather than being a crucial link in the process.
There's also one small optimization in XPath evaluation, and the maven POM that was broken in 1.2.3 should now be fixed.