On 8 January 2012 14:29, Adam Murdoch <[email protected]> wrote:
> > On 09/01/2012, at 3:46 AM, Daz DeBoer wrote: > > I think the recent code restructure has made some things unavailable to > our buildSrc project. I started to clean them up, but it wasn't as simple > as a few package changes. > Would be good to have a CI build that used the Gradle nightly to build > gradle. This would give us confidence to recommend the nightly to > bleeding-edge users. > > > Isn't this what our integration tests are for? > > The downside to using the nightly build to build from source is that it > becomes difficult for us to use internal or experimental stuff in our > build/buildSrc. > I'm not sure what you mean. I don't see how this would prevent us from using new features. On the contrary, we'd be forced to keep our build up-to-date with the latest experimental features and changes, which might be a pain. Perhaps it's that pain that you're referring to as "difficult"? I don't see the harm in finding out early when we've broken a feature that our build depends on. Chances are in this case we'll be breaking other people's builds as well. -- Darrell (Daz) DeBoer Principal Engineer, Gradleware http://www.gradleware.com
