Boilerplate project configuration in Gradle with Gradle Script Kotlin

plugins

(James Bassett) #1

I’ve asked this question on Stackoverflow (https://stackoverflow.com/q/43657807/1068649) and Kotlin’s Gradle slack channel, but haven’t got a definitive answer yet, so I’m trying my luck here :slight_smile:

For full details refer to the SO post, but the TLDR version is I’m after a better way of removing/sharing the boilerplate configuration from all of our gradle projects (in particular the configuration of our corporate nexus repository for both project dependencies and plugins, and making our custom gradle plugins available to every gradle project).

I’ve posted our current solution on that post, which works, but it makes me sad (it really feels like a hack).

I would love to hear from others who have solved this problem (knock knock anyone from Netflix?). In fact I’ve put up a 500 point SO bounty in case anyone needs the motivation :wink: