On 11/01/2013, at 2:51 AM, Luke Daley wrote: > Announcing this feature will force us to standardise on the term “evaluation” > or “configuration”. We use both interchangeably at the moment in different > places. > > I think it has to be “evaluate” as we use this in method names in our API > (e.g. BuildListener).
The term we're using now is "configure". We'll rename the existing usages of "evaluate" over time. > > Hate to do this again, but I'm wondering about the naming more generally. > It's currently enabled by setting “-Dorg.gradle.configuration.ondemand=true”. > Should we name this more generally to include optimising in general (e.g. > -Dorg.gradle.evaluation.optimize)? This would leave the door open for other > optimisations. I'm not sure. We could possibly rename it. There won't be a bunch of separate optimisations that you can switch on and off. There will be a single new configuration model that you can switch on. The aim is that this will be the default (and probably only) configuration model in Gradle 2.0. But 'optimize' isn't the right term, as the goal isn't about optimisation but about introducing a new decoupled configuration model which happens to have a bunch of nice properties, including being much faster. > > Begin forwarded message: > >> From: GitHub <[email protected]> >> Subject: [gradle-scm] [gradle/gradle] 73ebc5: Configuration-on-demand - >> cherry-picked a commit f... >> Date: 10 January 2013 9:23:28 AM GMT >> To: [email protected] >> Reply-To: [email protected] >> >> Branch: refs/heads/release >> Home: https://github.com/gradle/gradle >> Commit: 73ebc5540975393082b4dd5b0b7bf4c6196f41b9 >> >> https://github.com/gradle/gradle/commit/73ebc5540975393082b4dd5b0b7bf4c6196f41b9 >> Author: Szczepan Faber <[email protected]> >> Date: 2013-01-10 (Thu, 10 Jan 2013) >> >> Changed paths: >> M >> subprojects/core/src/integTest/groovy/org/gradle/api/ConfigurationOnDemandIntegrationTest.groovy >> M >> subprojects/core/src/main/groovy/org/gradle/api/internal/project/GradleInternalServiceRegistry.java >> A >> subprojects/core/src/main/groovy/org/gradle/execution/OnlyWhenConfigureOnDemand.java >> A >> subprojects/core/src/main/groovy/org/gradle/execution/ProjectEvaluatingAction.java >> A >> subprojects/core/src/main/groovy/org/gradle/execution/ProjectFinderByTaskPath.java >> R >> subprojects/core/src/main/groovy/org/gradle/execution/TaskNameDrivenProjectEvaluator.java >> A >> subprojects/core/src/main/groovy/org/gradle/execution/TaskPathProjectEvaluator.java >> M subprojects/core/src/main/groovy/org/gradle/execution/TaskSelector.java >> A >> subprojects/core/src/test/groovy/org/gradle/execution/OnlyWhenConfigureOnDemandTest.groovy >> A >> subprojects/core/src/test/groovy/org/gradle/execution/ProjectEvaluatingActionTest.groovy >> A >> subprojects/core/src/test/groovy/org/gradle/execution/ProjectFinderByTaskPathTest.groovy >> M >> subprojects/core/src/test/groovy/org/gradle/execution/TaskNameResolvingBuildConfigurationActionTest.java >> A >> subprojects/core/src/test/groovy/org/gradle/execution/TaskPathProjectEvaluatorTest.groovy >> >> Log Message: >> ----------- >> Configuration-on-demand - cherry-picked a commit from master. It includes >> some minor fixes, refactoring and bunch of coverage. >> >> >> Commit: 96889a5bf44a7010a673b63c7290c062e3ae6aca >> >> https://github.com/gradle/gradle/commit/96889a5bf44a7010a673b63c7290c062e3ae6aca >> Author: Szczepan Faber <[email protected]> >> Date: 2013-01-10 (Thu, 10 Jan 2013) >> >> Changed paths: >> M >> subprojects/core/src/integTest/groovy/org/gradle/api/ConfigurationOnDemandIntegrationTest.groovy >> M >> subprojects/core/src/main/groovy/org/gradle/api/internal/project/GradleInternalServiceRegistry.java >> M >> subprojects/core/src/main/groovy/org/gradle/execution/ProjectEvaluatingAction.java >> M >> subprojects/core/src/test/groovy/org/gradle/execution/ProjectEvaluatingActionTest.groovy >> >> Log Message: >> ----------- >> Configuration-on-demand - cherry picked from master. Corrected the handling >> of the default tasks in the COD mode. Now the default project is evaluated >> just like the root project is. After this change I think the COD is >> announcable as incubating. >> >> >> Compare: https://github.com/gradle/gradle/compare/0436ba272517...96889a5bf44a >> >> >> <hr/> >> <p> >> To unsubscribe from this list please visit: >> </p> >> <p> >> <a >> href="http://xircles.codehaus.org/manage_email";>http://xircles.codehaus.org/manage_email</a> >> </p> > > -- > Luke Daley > Principal Engineer, Gradleware > http://gradleware.com > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > -- Adam Murdoch Gradle Co-founder http://www.gradle.org VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting http://www.gradleware.com
