I'm generally not very keen on the name 'module'. It feels a bit too abstract, too ivy-like (a bit like ivy is leaking to the dsl). I think it may be somewhat confusing as 'module' is used elsewhere (for example, I heard people calling gradle multi-project builds a multi-module builds - sort of a maven style). I believe people coming from maven world think in artifacts and dependencies, not really 'modules'.
Not sure if we can find a better name instead of 'module' (or at least better 'external' name) but it would be cool to try :) Luke's SpecifiedDependency / NamedDependency works better for me than 'module'. > * 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. > I think moving away from 'module' and getting closer to 'dependency' is a good idea. Other suggestions: QualifiedDependency, VersionedDependency. > * The thing that the coordinates (group, module) refers to. This is also > called a module. > > > Tricky again. Maybe “NamedDependency”. > +1 for NamedDependency Cheers -- Szczepan Faber Principal engineer@gradleware Lead@mockito
