You can see this kind of thing in the Gradle source base itself for the subprojects.
On Wed, Feb 16, 2011 at 1:27 PM, Rene Groeschke <[email protected]> wrote: > Hi, > Am 16.02.11 18:12, schrieb Peter Niederwieser: > > Eventually figured it out. You are facing a Groovy limitation. If a > method > > defined like so: > > > > def foo(int[] args) { ... } > > > > is invoked like so: > > > > foo(1,2,3,4, ...) > > > > Then you can't have more than 255 method arguments. > > > > A simple workaround is to do the following in your settings.gradle: > > > > include "foo" > > include "bar" > > include "baz" > > ... > > > > If you have a Gradle build with more than 255 subprojects (and for a good > > reason), it might be time to think about other ways than to list each > > subproject explicitly. For example, you could scan the root project > > directory for subprojects. > We often have subprojects which have a common prefix like "myProjectAPI, > myProjectServices, myProjectUI. What about allowing wildcards in my > settings.gradle? this could end up in a settings.gradle file like this: > > ----- > include "myProject*" > ----- > > > regards, > René > > -- > > Peter Niederwieser > > Developer, Gradle > > http://www.gradle.org > > Trainer & Consultant, Gradle Inc. > > http://www.gradle.biz > > Creator, Spock Framework > > http://spockframework.org > > > > > -- > ------------------------------------ > Rene Groeschke > > [email protected] > http://www.breskeby.com > http://twitter.com/breskeby > ------------------------------------ > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > >
