It would be definitely great to support this for all model properties, not just task properties (and not just annotated properties either). The difficult part is to get the timing right: If you set the property to early, the path might not exist yet. If you set it too late, someone else might already have picked up the property's former value. But even if we just set the property at the very end of the configuration phase, this would already be a hugely helpful improvement.
The one advantage I see in limiting this to task properties is that it should be fairly easy to get the timing right (because task addition is observable). Other than that, it seems odd to support this for task properties but not for the "real" model. The String coercion requirement is just another reason to introduce a generic coercion service that's used in all model configuration. Cheers, Peter -- View this message in context: http://gradle.1045684.n5.nabble.com/spec-of-task-configuration-via-command-line-options-tp5710149p5710153.html Sent from the gradle-dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
