That looks reasonable for defining the artifact that contains the plugin. But then how do you define the repositories to look into for this jar? I would like to have a special tools or plugins repo, and maybe even a filesystem based way of getting the builds setup. Then the plugin can do all the smart magic.
-- View this message in context: http://gradle.1045684.n5.nabble.com/Ideas-for-simplifying-the-bootstrapping-of-plugin-loading-tp4588130p4588938.html Sent from the gradle-user mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
