Ok, "not yet supported" is an info I can deal with. I'll just use a shell script for now.
If I remember correctly, there was also the plan to get rid of settings.gradle in the future. It would be very nice if a future support would handle semi-external dependencies gracefully. With semi-external, I mean something like multi2/x depending on multi1/y. In case of a current/"normal" multi-module project, the dependency of multi2/x on multi1/y would be an external dependency but in a multi-multi-module (for lack of a better name) such a dependency should ideally morph into a project dependency, including up-to-date checks and so on. Hope this makes sense. Cheers, Joern. On 29.02.2012, at 04:22, Peter Niederwieser wrote: > In short, combining multiple builds isn't yet supported, but planned for > post-1.0. That said, with some effort you might be able to script a > solution. Two challenges I can think of are how to generate a combined > settings.gradle (unless it's OK to do it by hand), and how to handle project > vs. external dependencies. > > -- > Peter Niederwieser > Principal Engineer, Gradleware > http://gradleware.com > Creator, Spock Framework > http://spockframework.org > Twitter: @pniederw > > -- > View this message in context: > http://gradle.1045684.n5.nabble.com/Can-I-do-Multi-Multi-Module-builds-tp5521116p5523909.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 > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
