I still think it is pretty weird to include other ...

# kobalt

[edvin]

I still think it is pretty weird to include other dependencies embedded in a plugin, and I think there might be interesting license issues with this. The traditional approach is to bundle metadata with the plugin (eg pom.xml) so that the build system could download dependencies and setup the classpath before the plugin is run. I think you mentioned something about this not being a good fit for Kobalt somehow, is that right?