The ArrayUtil class is only meant to be used by the Groovy runtime, and unless there is a bug in the runtime, there shouldn't be any problems. I haven't followed the discussion you mentioned, but in general, such "ugly" code is typical for alternative language implementations on the JVM, and not automatically a sign of a problem.
Rene Groeschke wrote: > > The stacktrace of rodolfos exception would be useful here. > Yes. (Fortunately) I couldn't find any usages of ArrayUtil in Gradle code, so apart from a reproducible example, the stack trace is our best chance to find out what's going on. -- Peter Niederwieser Developer, Gradle http://www.gradle.org Trainer & Consultant, Gradle Inc. http://www.gradle.biz Creator, Spock Framework http://spockframework.org -- View this message in context: http://gradle.1045684.n5.nabble.com/The-maximum-number-of-directories-in-a-multi-project-envriontment-tp3387250p3387820.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
