On 31/01/2013, at 9:08 PM, Luke Daley wrote: > > On 31/01/2013, at 6:31 AM, Adam Murdoch <[email protected]> wrote: > >> Hi, >> >> I think we need a new name for the 'configure-on-demand' feature switch. >> What it actually does is enable a new decoupled project model, which Gradle >> can take advantage of to skip configuring projects that are not required, >> and also (optionally) execute stuff in parallel, and later do other >> interesting things like allow project dependencies in build script >> classpaths, build aggregation, and more. This new model will become the >> default in Gradle 2.0 (and, in fact, it is currently the definition of >> Gradle 2.0). >> >> So, I think what we need is some way to say 'please run my build with the >> new project model and switch on whatever nifty features this enables', >> rather than the current way to say 'please switch on this nifty feature and >> if that means using the new project model then thats ok'. Parallel execution >> is a bit of a special case and probably should keep its own flag. > > Makes a lot of sense. > > This seems to be hard to name. Left field idea… including some marketing in > this and calling it the Gradle 2.0 project model (opposed to the more > technical “decoupled”) and using that as the basis for the switch name?
We might even take this further, and allow the option to say something about the user's attitude to 2.0: - I don't care. Don't show me deprecations and warnings, it's not my concern. This might even be the default. - Let me know about things I can change to make my build more 2.0 like. More or less the current default. - This build is 2.0 compliant. Please make use of that. Warn me about cases where this is not the case so I can fix them. More or less the same as --configure-on-demand. - This build is 2.0 compliant. Please make use of that. Fail if this is not the case. The build comparison plugin might run the build with 'let me know' if the build would otherwise use 'I don't care'. -- Adam Murdoch Gradle Co-founder http://www.gradle.org VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting http://www.gradleware.com
