Hi,
I wonder whether Ant/Ivy has a "dependency fetching" mechanism like Maven
has
regarding "plugins". This is what I have in mind: A antlib provides
tasks
and macros and implements them in terms of 3rdparty libraries. Those
libraries
are described in dependencies (perhaps a la Maven). If such a antlib is
used,
Ant will download those 3rdparty stuff some cache directory and adjust
it's
classpath.
IMHO dependency fetching is the *worst* of the ideas that Maven has
popularised.
Instead of having a controlled build, you get a build where it's
possible that every single build is done against a different set of
artifacts
I prefer to know which libraries I'm building my code against :)
As for the problem you have, different organizations deal with the
problem in different ways.
1 - Place the full Ant (core) + extensions (antlibs etc) under version
control as a 'build' project - make this the only sanctioned way of
building the rest of your code
* This relies on allowing binaries into your scm - sorry *
2 - Use multiple build files and a complex arrangements of classloader
task, wget/get etc to pull in the correct dependencies for the build
3 - Edit the ant.bat|ant.sh
4 - Write a wrapper script that calls ant.bat|ant.sh with the correct
env setup
As you can see in other replies, the 'solution' varies depending on the
particular needs of the organization :)
Thanks,
Kev
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
