At work I’ve recently been tasked with figuring out how to backup and rename databases in the Berkeley DB store that’s in one of our middleware components. So I thought I’d try it out in JRuby. Getting the basics was surprisingly easy:
There are a few gotchas to be aware of. First keeping all your java includes in a module seems to be the best approach. I got somewhat flakey behavior when trying to do those import statements in the global scope. And second, don’t try to include java.io.File. It causes warnings about redefining File. I’m guessing because it has the same name as the ruby File class.
Next I had to make a standalone jar file so that our operations team could run it without installing JRuby. Sadly, this is not so easy. Rawr will allow you to package your ruby script into a jar, but the resulting jar doesn’t contain JRuby or any other jar dependencies. There’s also the rubyscript maven plugin, but that only stores ruby scripts into your system as maven mojos.
Neither of these solutions really fit, so I decided to just code it in java for now. For java projects, maven makes creating the standalone jar easy, as shown here. I’m thinking that between some of Rawr’s work and maven’s assembly plugin there’s a perfect solution. But I’ll have to do a bit more hacking to find it.