On Tue 2010-10-05 at 21:25h, Archie Cobbs wrote on ivy-user: : > Actually that's not quite right. The dependencies are not talking about JAR > files, they are talking about modules. : > *configuration* = a name that you give to some subset of the *artifacts* in > a *revision*; if none are defined "default" is the default and contains > everything; also determines how *dependencies* are resolved (see > *configuration > mapping*) > > *dependency* = depend relationship between a *revision* of a *module* and > other *modules*; has a *configuration mapping*
More precisely, due to configurations, dependencies are actually a relationship between (revisions of) sets of configurations, that is between subsets of modules' artifact sets. When resolving, one is always resolving s specific configuration, or set of configurations, not a module. Hence the nodes of the dependency graph are really (sub)sets of configurations, not modules. -- Niklas Matthies
