Peter Niederwieser wrote: > > Currently, only one settings.gradle is supported. You can still nest > multiple levels though: > > include "foo:bar:baz1" > include "foo:bar:baz2" > include "foo:zoo" > If you don't want to list all subprojects one by one, you can write some > code that includes projects automatically based on build.gradle files > found on the file system. > Hi Peter, is there any example somewhere? Some questions arisen after some attempts: * should I use the /gradle.settingsEvaluated/ closure on the root project to dynamically include sub projects? Since it seems it is never executed, I'm using /gradle.projectsEvaluated/, but maybe it's called too late... * how can I obtain a project instance once I've found the relevant gradle script? The api exposes only a ProjectBuilder... should I use some internal classes? * should I populate the /Project.childProjects/ map?
Cheers Davide -- View this message in context: http://gradle.1045684.n5.nabble.com/Nested-multi-projects-and-caveats-tp4480779p4802982.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
