Hi all! I probably should have been on this list some time ago, but at least I'm here now. No promises how closely I'll be monitoring, but I'd like to help foster more collaboration between JRuby and Buildr.
As Daniel posted, JRuby 1.5 is going to ship with full two-way integration of Ant and Rake. This is not your daddy's Antwrap...it's actually joining the two task/target spaces so they can be used simultaneously. Given that Buildr currently uses Antwrap to launch Ant targets, the new support may be a better backend. That URL again is http://www.engineyard.com/blog/2010/rake-and-ant-together-a-pick-it-n-stick-it-approach/ I have a few questions about Buildr as it stands today: 1. Is it possible to use Buildr without using any of its DSLs? The primary complaint I've heard from folks interested in Buildr is that it doesn't look anything like Rake, when they want to "just use Rake". But if all the key bits are available as Rake tasks, that shouldn't matter. 2. What's the reason for MRI/RJB support at this point? Daniel is right...the full two-way Ant/Rake integration does not support RJB, nor do we on the JRuby team have time to try to support RJB...but I'm wondering what benefit RJB actually gives you? In this case, it's very likely to hold you back. 3. The next obvious step for us in JRuby is to get better Maven/Ivy integration, both building upon the Ant/Rake integration and for RubyGems. But we're Maven neophytes, so ideally we'd be able to just reuse or share parts of Buildr to do all that. We'd rather not have JRuby ship a complete set of build tools that are totally independent of Buildr, since that would just fragment and confuse. Anyway, I'll try to monitor this list and hopefully we can work together more closely in the future. - Charlie
