i would like to do that too ... for now i build a customized gradle-distribution (zip) and publish it on a shared volumn.
gradle-users are triggered by mail if distribution has changed. mvlcek wrote: > > Thank you, I know that I can customize a plugin or add code in buildSrc. > > However, this requires each developer to copy the customization, whenever > it changes or is improved or - in the case of buildSrc - to copy the > customization to every project. > > Instead I want to have one file with customizations lying on a central > server (e.g. the repository server). > > Then it should be possible to include all the functions within it with a > simple > - include(repositoryPath + '/configuration.groovy') > - configure(project) > or similar. > > The developers just have to set the repository path as property and if a > new version of the configuration code is necessary they will automatically > use it with the next build. > -- View this message in context: http://www.nabble.com/Common-functions-in-external-file--tp20131097p20133610.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
