> My impression was, GUMP always use the cvs-head to build the
> dependencies - and fixing the dependency to a given release
> is not the intention of GUMP.
>From experience, I can tell you that I welcome the new ability to fix
certain dependencies. For example, the Avalon Project has made API changes
that break compatibility with existing code. James ships with an earlier
version of Avalon because of the incompatibility. Eventually, James will
make the necessary changes, but that will happen on James' schedule, not
Avalon's. But James also ships with Jakarta Commons DBCP, and will be using
other Jakarta Commons packages. If James were forced to track the HEAD of
all components, even when some of them are known to be incompatible, there
would be no point in using GUMP, since failure can be assumed. However,
with the new ability, James could fix the Avalon dependencies to the
particular version(s) used, and still track HEAD for other dependencies.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
