You could factor out the commonalities between the builds into, say, buildSrc/gradle/common.gradle, and apply that script from both builds with "apply from:" followed by the relative path to common.gradle.
-- Peter Niederwieser Principal Engineer, Gradleware http://gradleware.com Creator, Spock Framework http://spockframework.org Twitter: @pniederw Russel Winder wrote: > > There are times when a dependency has to appear in both build.gradle and > buildSrc/build.gradle. It seems a violation of DRY to have to repeat > the same constants in both places. What is the approved idiom for > sharing global data between these files? > > Thanks. > > -- > Russel. > ============================================================================= > Dr Russel Winder t: +44 20 7585 2200 voip: > sip:[email protected] > 41 Buckmaster Road m: +44 7770 465 077 xmpp: [email protected] > London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder > -- View this message in context: http://gradle.1045684.n5.nabble.com/data-coupling-build-gradle-and-buildSrc-build-gradle-tp4735258p4740113.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
