Merlyn Albery-Speyer wrote: > > The property is called excludes not exclude >
At the moment you can either use: exclude "foo" exclude "bar", "baz" or: excludes = "foo" excludes = ["bar", "baz"] The latter will overwrite previously configured excludes. Merlyn Albery-Speyer wrote: > > It would be less powerful and more newbie-friendly to be able to fail > when a task property does not exist. Perhaps the ability to turn off > the dynamic property creation for debugging purposes? > This has already been discussed a few times. At some point, Gradle will definitely become smart enough to tell you what the problem is. -- Peter Niederwieser Developer, Gradle http://www.gradle.org Trainer & Consultant, Gradle Inc. http://www.gradle.biz Creator, Spock Framework http://spockframework.org -- View this message in context: http://gradle.1045684.n5.nabble.com/Is-there-a-way-to-prevent-dynamic-creation-of-task-properties-tp3396391p3396423.html Sent from the gradle-user mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
