On 06/09/2012, at 3:13 PM, Szczepan Faber wrote: > Hey guys, > > I drafted a (somewhat internal) spec for task configuration via > command line options. > > https://github.com/gradle/gradle/blob/master/design-docs/task-configuration-from-command-line.md > > This is driven by a dependency report I'm working on.
It will be great to have this feature. What you have in “Implementation plan” is not really an implementation plan, they are more acceptance criteria. I wonder if we can get away with simply being able to set any “addressable” property with a string value. You can kind of think as the Project as a graph… (project.).thing1.child1.anotherchild.property = "foo" So something like… ./gradlew dependencyInsight +dependencyInsight.configuration=testCompile Or maybe a shorthand if you want to invoke a task and set something… ./gradlew dependencyInsight+configuration=testCompile Not saying this should be the exact syntax, it probably shouldn't. The idea being that anything that is addressable via a key path is fair game… ./gradlew check +test.maxParallelForks=4 To make this useful we'd at least need a good way to coerce from string in a fairly flexible way. For example, if my property is a Configuration and you give me a String I know to look for project.configurations[«string»]. -- Luke Daley Principal Engineer, Gradleware http://gradleware.com --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
