Would that also be a step toward aggregate builds? On Thu, Sep 29, 2011 at 15:53, Adam Murdoch <[email protected]>wrote:
> > If we had a little more time available, I'd change Project.childProjects, > subprojects and allprojects into DomainObjectCollections, and add a > Project.childProjects.add() method. This would be the first step in getting > rid of settings.gradle. > > > On 30/09/2011, at 3:21 AM, Szczepan Faber wrote: > > >Only that we have to be careful about what we expose publicly. > > Ok. So it's a method that creates a child project. > > Cheers! > > On Thu, Sep 29, 2011 at 6:32 PM, Luke Daley <[email protected]>wrote: > >> >> On 29/09/2011, at 5:26 PM, Szczepan Faber wrote: >> >> I'm planning to move HelperUtil.createChildProject into the >> ProjectBuilder. This way other projects can do some more interesting testing >> :) >> >> Let me know if you have any objections. >> >> >> Only that we have to be careful about what we expose publicly. >> >> -- >> Luke Daley >> Principal Engineer, Gradleware >> http://gradleware.com >> >> > > > -- > Szczepan Faber > Principal engineer@gradleware > Lead@mockito > > > > -- > Adam Murdoch > Gradle Co-founder > http://www.gradle.org > VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting > http://www.gradleware.com > > -- Jason Porter http://lightguard-jp.blogspot.com http://twitter.com/lightguardjp Software Engineer Open Source Advocate Author of Seam Catch - Next Generation Java Exception Handling PGP key id: 926CCFF5 PGP key available at: keyserver.net, pgp.mit.edu
