Jose,
On the topic of Groovy, yes, that would change the playing field completely. I'm also intrigued by
Buildr, but I'm not sure in either case if I'm ready to go into that territory yet. For one, I don't know Groovy or Ruby very well, and while the learning curve I'm sure is gentle, I'm interested in just how far you can get with the simplicity of Ant. Ant is definitely limiting, but within those limitations I like to see what can happen.
On the topic of multi-project support, while I have some ideas for that, there is nothing in the works right now. I agree that it would be very useful to see the feedback results for a collection of components, with the ability to drill down to individual projects. The idea for Glean actually came from a project I was on where I had put together a build process to gather feedback for the 15+ components that made up our application, and in the end it wasn't that pretty. My goal with Glean was to start over and focus on getting it right for a single component project first, and build from there.
Getting it to work with multiple projects would certainly be easier with a dynamic language in the script, but as I said above, I'm a little hesitant to make that step. Then again, maybe that is something that is just another optional element to Glean, where people who want that support (multi-project feedback, in this case) are willing and able to take on the dependency of Groovy. I did it for the Dashboard because that seemed like a really compelling need, something that I have certainly wanted to have for a long time,
I hope that helps. If you have any suggestions of particular things you'd like to see for collective feedback on multiple projects, I'm open to suggestions and ideas.
Thanks,
John