Yes, exactly. I have a single line buildscript entry now for grabbing the
plugin jar from the SCM workspace while I am working out the details of
bootstrapping. Like this:
buildscript { dependencies { classpath fileTree(dir:
'../../../Tools/nebula/build/libs', include: '*.jar') }}
But it could get more sophisticated, so I would like to make it centralized
and reusable. I can see wanting to have it setup the classpath automatically
to get all of our build plugins from a number of possible places, and for
different levels of stabilities. Once the users' build.gradle scripts have
the right buildscript classpath, everything else can be done in the plugins.
--
View this message in context:
http://gradle.1045684.n5.nabble.com/Ideas-for-simplifying-the-bootstrapping-of-plugin-loading-tp4588130p4594982.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
