ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hugo Pinto <>
Subject Re: Why should I use a dependencies manager?
Date Sun, 07 Feb 2010 15:42:24 GMT
Hi Cby,

Just think about projects which use subprojects which have
dependencies not compatible with the parent project's dependencies(or
deprecated versions of common libraries) and you've got a case where
you need to manage your dependencies formally.

If you have a single project it may be overkill(*); have many projects
that may be combined or have dependencies between them and you will
need some sort of dependency management.

(*) I use for all my projects though, as in practice I use so many
framweworks as to always fall into the case of a "project that uses
other projects that have umpredictable dependencies"

Hugo Pinto
Artificial Intelligence, Computational Linguistics and Computer Games

2010/2/7 CBy <>:
> Hi,
> I like to setup my projects in such a way that new users can check them out
> from our subversion repository and are ready to go. For managing
> dependencies, I have been experimenting with both Maven Ant Tasks and Ivy.
> Now that I have to choose between them, I seem to have forgotten why I
> started this exercise in the first place. Granted, checking in log4j and
> other libraries that I use in almost every project is not very efficient,
> but who cares? It's simple, has none of the bootstrapping problems, and disk
> space is not really a concern nowadays. I like simple. Is there a compelling
> reason not to do it this way? (I've read the FAQ, but was not really
> convinced so far.)
> CBy

View raw message