Hm… I don't use separate build files for multi-module builds at all. Instead, I put the definitions for all modules into the same build file. Is this really uncommon?
I always considered this a major improvement over Maven. Cheers, Joern. On 19.01.2012, at 02:57, Luke Daley wrote: > The gradle build itself is also configured this way. > > On 18/01/2012, at 5:35 PM, Steve Ebersole <[email protected]> wrote: > >> I do the same for Hibernate and it has nothing to do with not liking the >> phrase build. I just prefer that convention over multiple files named >> build.gradle opened in my.editor simultaneously. >> >> [email protected] >> http://hibernate.org >> >> On Jan 18, 2012 6:51 PM, "Kris De Volder" <[email protected]> wrote: >> Correction.. my memory was faulty. The project I was thinking about is >> spring-security >> >> The root project has some stuff in the settings.gradle file like this: >> >> def String[] samples = [ >> 'tutorial', >> 'contacts', >> ... >> ] >> >> include samples >> >> samples.each {name -> >> p = findProject(":${name}") >> def fullName = name.replaceAll('/','') >> p.name = "spring-security-samples-${fullName}" >> p.buildFileName = "${fullName}.gradle" >> p.projectDir = new File(settingsDir, "samples/${name}"); >> } >> >> Kris >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
