You can put the commonalities in a build script served from a file or HTTP server and apply it with "apply from: ...". Note that these scripts aren't cached at the moment, so if the HTTP server or network connection is down the builds won't work.
If you find yourself sharing lots of properties, consider writing and sharing your own plugins and/or tasks instead. Otherwise you might end up with Ant-like builds with lots of explicit, low-level configuration. -- Peter Niederwieser Principal Engineer, Gradleware http://gradleware.com Creator, Spock Framework http://spockframework.org Twitter: @pniederw Etienne Studer wrote: > > Hi > > I'm not sure what is the best way to define and share some properties > across independent projects. > > For example, I have two projects A and B that I build with Gradle and for > each of them, I want the properties aaa=..., bbb=..., ccc=... be available > as project properties on each project. > > Is there a way I can put a properties file somewhere on a web server and > then reference it from different Gradle builds such that these properties > become project properties? > > Any help is kindly appreciated. > > Kind regards, Etienne > -- View this message in context: http://gradle.1045684.n5.nabble.com/How-to-share-properties-across-projects-tp4744577p4744667.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
