On 29/10/2011, at 7:13 AM, Adam Murdoch wrote: > Hi, > > > 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). > > * 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. > > * The thing that the coordinates (group, module, version) refers to. > Currently, this is called a module.
I think for now we will call this a 'module version'. > > * The thing that the coordinates (group, module) refers to. This is also > called a module. I think for now we will call this a 'module'. So, we have: * A module has one or more module versions. * A module version has one or more configurations. * A module version may be published to a repository. * A dependency refers to a configuration in a module version. * An external dependency refers to a configuration in a published module version. * A Gradle project produces a module version. * A project dependency refers to a configuration in the module version of a local project (this needs some refining, but will do for now). I'd like to sort out this terminology for m6. -- Adam Murdoch Gradle Co-founder http://www.gradle.org VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting http://www.gradleware.com
