w On 19/11/2012, at 6:55 PM, Adam Murdoch wrote: > > On 20/11/2012, at 4:20 AM, Luke Daley wrote: > >> http://issues.gradle.org/browse/GRADLE-2542 >> >> Can someone who is more knowledgeable in the dependency resolution stack >> please take a look at the above request? >> >> In short, what they want to do is allow the descriptor for a module to >> express that it's a different version than what was expected. >> >> e.g. >> >> compile "foo:bar:default" >> >> When this is resolved, the descriptor will provide a concrete revision >> number. Our code will throw an exception when a module provides an >> unexpected revision. >> >> My initial thought is to push back and find another way, but I want to >> verify first that our behaviour is intentional and we don't want to allow >> this behaviour before investing more time. > > Exactly right. Seems like they could use the 'libraries' approach that we > use. We certainly don't want people using custom Ivy DependencyResolver > implementations to solve this problem, even if we think that doing this down > at the repository level is the right way to go (which I don't think we do).
From what I understand of the issue, the indirection is at the repository level, where as with the 'libraries' approach it is client side. Anyway, that's enough for me to go back to the ticket with. -- Luke Daley Principal Engineer, Gradleware http://gradleware.com --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
