Bushel: Making OSGi bundle management easier with Ivy

I've decided to start building an application in my so called spare time, to see if I can make a business out of it in the long term. I'll reveal more about the application, if and when I have something interesting to show. The app is currently being developed using the Eclipse RCP and OSGi, mainly because I was keen to learn how to use these technologies to build an application. So far it's been a bit of a struggle to figure out the best way to layout a project, manage bundle granularity and a few other best practice things. The first problem I came across was, how to manage my dependencies. As much as I like using the Eclipse PDE, I still prefer to have an Ant script to build my application. In particular when I get a build server up and get some continuous integration good-ness happening. So, how do I collect only the bundles I am using in my application, in one place, with minimal fuss, and easily add new bundle dependencies, without manually copying files? Well, this has been solved with plain jars, just look at Maven or Ivy. But bundles are still relatively new and the best practice is still evolving... we'll as far as I can tell anyways. I chose to use Ivy, because it's a little less opaque than Maven. I won't say it's better. It's just more my flavour. So, I've slapped together an Ant Task to help build a local Ivy repo from ad-hoc bundles. I've made it freely available from here. And you can get a more detailed example of what I am doing in the following tutorial. I'd be keen on feedback, especially if anyone know of a better way to do what I'm doing. I've google'd as much as I care to on the topic and didn't find any solutions. So any tips would be much appreciated. A.