Adam Murdoch wrote:
>
> I wonder if we might take advantage of the wrapper here, to provide some
> conventional place to find and execute this bootstrapping logic.
>
> For example, perhaps the wrapper looks for a
> ${distributionDownloadLocation}/init.gradle when it downloads the
> distribution, and if found, applies this init script when it invokes
> Gradle. We'd combine this with improving the init script DSL.
>
> To provide custom organisation-wide logic, you'd publish a Gradle
> distribution and an init script to some location, and point your builds at
> this location.
>
Yes, this sounds like a very workable approach. We can then use a standard
Gradle, our custom plugin(s), and a small init.gradle that we deliver as
part of the wrapper bundle.
--
View this message in context:
http://gradle.1045684.n5.nabble.com/Ideas-for-simplifying-the-bootstrapping-of-plugin-loading-tp4588130p4614014.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
