On 29/12/2012, at 9:27 PM, Adam Murdoch wrote: > > On 21/12/2012, at 2:15 AM, Luke Daley wrote: > >> >> >> On 18/12/2012, at 11:28, Adam Murdoch <[email protected]> wrote: >> >>> >>> On 19/12/2012, at 3:57 AM, Daz DeBoer wrote: >>> >>>> G'day >>>> There's been a bit of discussion about what is the best name for what >>>> is currently referred to as "Dependency Resolve Actions". >>>> Docs for this new feature are at >>>> http://gradle.org/docs/nightly/userguide/dependency_management.html#sec:dependency_resolution. >>>> >>>> One suggestion (mine) is "Dependency Resolve Hooks", since this is a >>>> way for you to hook into the dependency resolution process. >>> >>> My suggestion is 'dependency resolve rules'. >> >> What's the scope of this "hook"? Is it limited to affecting what actually >> gets resolved? > > Pretty much. It is given a module version selector that has been requested, > and given the opportunity to change that selector in whatever way it likes > (changing version, or module, or group). Once the selector has travelled > through all the rules, resolution proceeds as normal.
I can't come up with anything better than “rule”. It's conceivable that DependencyResolveDetails might get some more behaviour later (e.g. exclude(), transitive = false) I think generalising on the term “rule” makes sense. -- Luke Daley Principal Engineer, Gradleware http://gradleware.com --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
