On 01/04/2012, at 3:07 AM, Szczepan Faber wrote: > This sounds cool. > > * treat 403 and 405 HEAD requests as "metadata unknown" > * if the server is googlecode, treat 404 HEAD requests as "metadata unknown" > > Just double-checking. With this approach, i.e. special casing only googlecode > are we compatible with the previous milestones wrt getting remote binaries?
Dependency resolution didn't actually work with googlecode.com before, when you didn't have an ivy.xml/pom.xml - you'd get a 'module not found'. Now, resolution should work. For the other cases, everything should resolve more or less as it did previously. The upside of this change is that we can now check for changes to http resources that don't have an associated .sha1, such as ivy repositories, ad hoc artefacts that aren't in a repo, and so on. This, for example, makes --refresh-dependencies usable when you're using a remote ivy repository, and if this repo is backed by Artifactory, you get reuse of local candidate artefacts, too. However, we are now much more dependent on the server having a reliable HEAD method implementation. Let's see how we go ... -- Adam Murdoch Gradle Co-founder http://www.gradle.org VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting http://www.gradleware.com
