ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mitch Gitman <>
Subject Re: Use ivy-dependencies to create ant-tasks
Date Wed, 10 Mar 2010 15:27:51 GMT
The approach I've seen and I like is to use one Ivy module descriptor for
the project proper and another one for the build. So, if you're just calling
your ivy.xml ivy.xml, you might have:
* ivy.xml: project-proper dependencies
* build-ivy.xml: build dependencies

To me, the really compelling reason for creating this separation is that
you'll probably find that your build dependencies rarely vary between
projects while your project dependencies are very much project-specific. So
you're better off copying a common build-ivy.xml or build.ivy into each
project--or better yet, consuming a single copy from a common location--than
you are always copying those build dependencies into your ivy.xml.

And what you'll find happening too if you put your build dependencies in
your project ivy.xml is that the former could end up swamping the latter
since there are many projects that just don't need a lot of dependencies.
And for those projects that do, having all those build dependencies in there
too makes the module descriptor that much more complicated, even though you
can follow conventions to clearly state which dependencies belong to the

There are various nice things you can do to further enforce this separation
between project and build dependencies. Anyway, this should get you going...

On Wed, Mar 10, 2010 at 6:26 AM, marcdb <> wrote:

> Hello,
> We are using an ant-task called wsimport to create java-classes from xml.
> This wsimport task is defined as follows in our build-file:
> <taskdef name="wsimport" classname="">
>         <classpath refid="jaxws.classpath"/>
> </taskdef>
> Where classpath points to the appropriate jaxb and jaxws jars which are
> checked-in in our version control system.
> To control the version of jaxb and jaxws jars that we are using for making
> our builds, we were thinking about using the ivy-dependency mechanism: via
> an ivy.xml file for the build-system, the appropriate versions of these
> jars
> would be retrieved, which could then be used in the classpath when making
> the taskdef.
> Has somebody already done this or knows a better solution to manage the
> versions of the jars that are used in taskdefs of build.xml files.
> Thanks,
> Marc
> --
> View this message in context:
> Sent from the ivy-user mailing list archive at

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message