I put the finishing touches on the second release of one of my open-source projects, Moo, last night. I'd been updating the documentation for a few weeks now to get that in sync with all the code changes that have been taking place. Now that it's finally done, I've released Moo v2.0 up to the Maven central repository.

Moo v2.0 is the first release that was driven more from requests made by users of Moo than for my own needs. If you're using Moo and you'd like to make a request, get in touch over email, twitter, or GitHub, and I'll see what I can do.

For those of you already using Moo, I'd love to hear some thoughts about how Moo v2.0 works for you and what enhancements you still need.

If you're not using Moo, it's a relatively unintrusive way of mapping one object graph to another in Java. Check out the website, the release notes or the wiki to learn more.

I've released the first release candidate build of Moo v2.0, which can be found in Sonatype's OSS staging repository if you use Maven, or you could just download one of these JARs directly from the repo:

• moo-core-2.0-rc-1.jar
• moo-mvel-2.0-rc-1.jar

I released v0.3 of my Tunnel Boring Machine (site, github, rubygems) this morning. The primary change you'd notice as a user is a simpler way to configure aliases for targets. There's a little more going on under the covers, and you can read my release notes if you feel so inclined.

I released v0.2 of Tunnel Boring Machine for managing SSH tunnels. The core of this release is a significant improvement to the configuration file for my needs and the needs of the people I'm currently working with, although you can read through the GitHub issues if you want to know more.

I feel like the configuration file format is also stabilizing, so I've documented it reasonably thoroughly. There isn't that much left on my planned scope for v0.3, so I'll probably get that out sometime in the next month or so, although I do have some other things on my plate that will have to get done first.

Yesterday, I released v1.2.0 of Prune, which you can install and use as a Ruby gem, if you are so inclined. My updated summary of Prune says:

Prune is designed to maintain a file tree, pruning files by removing and archiving them when necessary.

Prune came from my own need when working with a project that made nightly backups. I wanted to retain the most recent two weeks of backups, retain the Friday backups for anytime older than two weeks within the current and previous month, archive all friday backups from months earlier than the current and previous months, and remove non-friday backups older than two weeks.

I'm still using prune with the same client project for the same purpose, it's going strong. This latest release was primarily around configurability -- I wanted to cut down on the verbosity of the output for my nightly batch pruning without affecting its utility as an interactive command-line application. Prune is much more configurable and much easier to configure than it was in release v1.1.1. You can read the full release notes on the blog.

There's nothing pressing for me in candidate releases for v1.3.0 and v2.0 that I've been tracking in github. There are things I'd like to get to, but nothing that I need. As a result, if you're using prune, or you'd like to, but you'd like a feature to be added, now's a good time to suggest it.