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. I thought maybe customizing the wrapper could work, or sneak in an init script somewhere else. Anybody else doing something like this? --carl -- View this message in context: http://gradle.1045684.n5.nabble.com/Ideas-for-simplifying-the-bootstrapping-of-plugin-loading-tp4588130p4588130.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
