On 28/10/2011, at 9:13 PM, Adam Murdoch wrote: > We need some better names for the following things, as we head in towards > Gradle 1.0: > > * The thing that represents a logical set of incoming dependencies. In the > API, this is at various times called a Configuration or a > ResolvableDependencies (also a ResolvedConfiguration).
What's the relationship between this thing and DependencySet? > * The thing that a dependency refers to. Currently, these are called > 'configurations', and each configuration lives in a 'module'. These are not > the same as the 'configurations' above, but they are related (ie the incoming > dependencies almost always become the outgoing dependencies). In the API, > this is called a Configuration, or a ResolvedDependency. I don't quite follow here. Is this about mapping a logical name to a set of physical files? > * The thing that the coordinates (group, module, version) refers to. > Currently, this is called a module. Tricky. Maybe “SpecifiedDependency”? The key point that all the information has been given to fix on a specific instance of a dependency. > * The thing that the coordinates (group, module) refers to. This is also > called a module. Tricky again. Maybe “NamedDependency”. I'll keep thinking on it. Coming up with good names in this area would be *very* helpful for our users and also other developers. -- Luke Daley Principal Engineer, Gradleware http://gradleware.com
