On 26/10/2012, at 8:16 PM, Luke Daley wrote: > See > https://github.com/gradle/gradle/blob/master/subprojects/core/src/main/groovy/org/gradle/api/artifacts/dsl/RepositoryHandler.java#L202 > > Are we planning to do something about this?
Yes. It'll get removed at some point. There are a few use cases you still need to use an ivy resolver for, so we'd need replacements (or not) * sftp and webdav repositories. * some of the layout tweaks that Ivy allows. I think the only thing left here is an equivalent to m2compatible. * some of the metadata tweaks that Ivy allows, such as which types of meta-data (if any) to consider, whether a module is changing or not, versioning strategy for a module. We'd need to implement solutions for some of these via our DSL, deprecate the use of Ivy resolvers and later remove resolver from the API. > In Gradle 2.0 are we planning on having DependencyResolver be part of our > public API? Depends how much of the above we've done at the time we're considering doing a 2.0 release. I'd much rather it was not part of the 2.0 API, but it's not necessarily a blocker for 2.0. -- Adam Murdoch Gradle Co-founder http://www.gradle.org VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting http://www.gradleware.com
