Hi Johan, thanks for your suggestion. I fear this project/folder structure won't work out for me, because my company already has an existing folder layout. It's described in http://gradle.1045684.n5.nabble.com/How-to-set-up-multi-product-builds-tp4716825p4716825.html this previous thread .
However, your post brought me the idea of a fourth alternative: d) Use a standard build.gradle file for one release and an build73.gradle file for the other. Are there any other opinions out there? I am still wondering if there is a recommended strategy for this issue. Best regards, Björn -- View this message in context: http://gradle.1045684.n5.nabble.com/How-to-create-distributions-with-different-dependencies-and-different-outputs-tp4741969p4747963.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
