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.
By the way, subprojects {} refers to all direct and indirect children. To
only configure the direct children, use childProjects {}.
--
Peter Niederwieser
Principal Engineer, Gradleware
http://gradleware.com
Creator, Spock Framework
http://spockframework.org
Blog: http://pniederw.wordpress.com
Twitter: @pniederw
Paul wrote:
>
> Can someone give an overview of how nested multiprojects are supposed to
> work?
>
> I have tried for a few days at nesting multi-projects but can't seem to
> find the magic formula that will pick up ALL subproject tasks with a given
> name.
>
> The goal is to be able to add/remove nested multi-projects at any level in
> a directory structure without having to configure settings.gradle files at
> various levels.
>
> Is something like this off limits (sub projects at any level may be
> multi-projects themselves)?
>
> dependsOnChildren()
>
> build.gradle:
> task hello << {
> println "1"
> }
>
> subprojects { subProj ->
> task hello << {
> println "2"
> }
> subProj.subprojects { subSubProj ->
> task hello << {
> println "3"
> }
> }
> }
>
--
View this message in context:
http://gradle.1045684.n5.nabble.com/Nested-multi-projects-and-caveats-tp4480779p4480834.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
