On 25/10/2010, at 10:30 PM, David Resnick wrote: > The user guide mentions at 32.2.3. > (http://www.gradle.org/latest/docs/userguide/dependency_management.html#sec:dependency_management_overview > under "Version conflicts") that the default resolution strategy for > dependency version conflicts is to use the newest version. How can I > change the strategy used? Is there any way to cause the build to fail > when conflicts are encountered?
Not yet. Could you add a JIRA issue for this? -- Adam Murdoch Gradle Developer http://www.gradle.org CTO, Gradle Inc. - Gradle Training, Support, Consulting http://www.gradle.biz
