Sure, I was planning on doing it in stages. These seem reasonable to me, thanks for the suggestions. I'll start work on this ASAP (which may end up being this coming Monday...).
On Wed, Aug 5, 2009 at 6:23 PM, Adam Murdoch <[email protected]> wrote: > > > John Murph wrote: > >> I think we have reached enough consensus that I can start working on this. >> I'm a little concerned about the technical implications of moving Build >> (soon to be GradleInvocation? -- which I like) to be created earlier. I >> might need some help with that when I get to this task. >> > > Any chance you could do this in a few steps? We could move Build first, get > that merged in, and then add the init script, and then make the Build > interface richer so it does the stuff you need. > > Moving Build shouldn't be a big deal. You'll need to do something like: > - Replace the root project constructor parameter with a setter, and change > the getter to throw an exception when not available. > - I'd move the buildSrc classloader stuff from BaseSettings to a > ScriptClassLoaderProvider implementation. We need this moved out for a > number of reasons. > - Change BuildLoader.build() to be passed a BuildInternal to populate, > rather than returning a BuildInternal. > - Maybe change BuildListener.buildStarted() to take a Build rather than a > StartParameters as an argument. > > > > Adam > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > -- John Murph Automated Logic Research Team
