On 17/07/2011, at 9:32 AM, Eric Berry wrote: > I've run into this issue myself. Right now I'm having our developers download > the plugin jar file and install it into gradle lib/plugins directory. But the > buildscript method seems pretty standardized. > > I wonder if it could be automated more by adding something like: > apply plugin: 'company-plugin', fromJar: 'url://to/company-plugin.jar' > > I was looking through the source recently, and I was thinking it might be > possible to add something like this to the DefaultObjectConfigurationAction. > > Where it would download the jar to ~/.gradle/cache (or somewhere else), and > then add a buildscript closure to the project pointing the dependency at the > downloaded jar file. > > Afterwards applying the plugin. > > I'm not completely familiar with the Gradle source, but is something like > this even feasible? If so, I can try and get something working over the next > week or so and try to submit a patch?
This thread and the “easy plugin integration” thread are highlighting that there is a hole here. Before working on any implementations or even DSL modifications, I think we need more thought and exploration of the core problem here. The best way to do that is probably to explore people's use cases and see what patterns emerge. To that end, it would be useful to get some information on the nature of your project and how you are using the plugin mechanism to solve build problems, including the development workflow. -- Luke Daley Principal Engineer, Gradleware http://gradleware.com --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
