On 15/07/2011, at 6:58 AM, cquinn wrote: > Im in the process of moving some shared Gradle scripts into one or more > plugins for my company's common build system. This is all going to replace a > bunch of shared Ant scripts. > > One advantage of the shared scripts is that it was super easy for any > project to just import (Ant) or apply from (Gradle) one script file, and > then voilà. > > With the Gradle plugin(s), the apply is easy, but the buildscript classpath > has to be defined first. So, I would like to provide a really simple way for > the users to magically get the 'right' classpath. And maybe one for > development version locally built, and one for the released versions in the > repo.
What does your ideal user syntax look like? > I thought maybe customizing the wrapper could work, or sneak in an init > script somewhere else. > > Anybody else doing something like this? -- Luke Daley Principal Engineer, Gradleware http://gradleware.com --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
