On Tue, Oct 5, 2010 at 12:03 PM, David Sills <[email protected]>wrote:
> <dependencies> > <dependency org="org.apache.log4j" name="log4j" rev="1.2.15" > conf="javac,test->default"/> > <dependency org="net.sourceforge.jibx" name="jibx" rev="1.2.2" > conf="base->runtime-xpp3,extras;bind->bind"/> > <dependency org="org.xmlpull.xpp3" name="xpp3" rev="1.1.3.4.O" > conf="javac->default"/> > </dependencies> > > I understand that this means: > > 1. There are 3 dependencies for the module. > 2. The JAR file log4j-1.2.15 is required in some cases. > 3. The JAR file jibx-1.2.2 is required in some cases. > 4. The JAR file xpp3-1.1.3.4.0 is required in some cases. > Actually that's not quite right. The dependencies are not talking about JAR files, they are talking about modules. Glossary: *module* = some software with a name; has multiple *revisions* *revision* = a specific release/instance of a module; contains one or more * artifcats* *artifact* = a file, often a JAR but can be anything (e.g. sharedlib.so, XML file, etc.) *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* *configuration mapping* = in a given *dependency*, describes which * configurations* of the other *module* are required for each *configuration*of the current *module* -Archie -- Archie L. Cobbs
