ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Sills" <>
Subject RE: Question about documentation
Date Tue, 05 Oct 2010 17:03:20 GMT

Thanks so much for your example. However, there's still a lot I don't
understand. Let's start with the (simple?) first thing:

        <dependency org="org.apache.log4j" name="log4j" rev="1.2.15"
        <dependency org="net.sourceforge.jibx" name="jibx" rev="1.2.2"
        <dependency org="org.xmlpull.xpp3" name="xpp3" rev=""

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- is required in some cases.

After that, I part company from understanding.

It seems to me that the "conf" attribute means:

5. The JAR file log4j-1.2.15 is used in the javac and test
configurations. I have no idea at all what "->default" means, and the
discussion in the documentation has successfully confused my entire
office. Perhaps a bit of clarification might be possible?
6. The JAR file jibx-1.2.2 is required in the javac, test, and runtime
configurations by virtue of being required in base. What "bind->bind"
means is completely obscure. Again, what "->runtime-xpp3,extras" means
is also not clear - these are not configurations that are defined in
your file, so I would hazard a guess that they must be defined in some
Ivy file at the "net.sourceforge.jibx" organization in the Google code
repository (guessing based on ivysettings.xml). If this is correct, how
on earth can one keep track of other people's Ivy files, which I presume
may change at will?
7. The JAR file xpp3- is required in the javac configuration
(that is, not for runtime or test). Again, "javac->default" is not
clear, as no default is defined in this file (but may be somewhere else,
as before).

I understand quite well what the file is supposed to do - the overall
concept is clear, it's the little things, like this.

Any help would be gratefully received.

David Sills

-----Original Message-----
From: [] On Behalf
Of Archie Cobbs
Sent: Tuesday, October 05, 2010 11:50 AM
Subject: Re: Question about documentation

Maybe a simple example would help?

If you are familiar with ant, then you should be able to decode this
project <>. All it
is use ivy to pull in a few JARs during the build, test, etc. phases. It
uses some included ant macros to simplify the build.xml, etc. The ivy
are under trunk/src/ivy.

There is a separate "public" ivy file that is used to represent this
module in a repository, which is viewable (styled as HTML)


View raw message