Hello Just a little answer to your question ... I personnaly use retrieve task fro bring back all dependencies in my project , but i define specifics configurations for each kind of artifact my project will generate for example, in one of my project , i have a "client" configuration and an "application" configuration each of them will be "retrieve" in a specific subdir of "lib" directory ...
All i need to do after that is to create some filelist or path with ant . In this case if a dependency have to be modified , i just have to modify the ivy file, but the build file remains inchanged... HTH Greg PS : BTW this case could leave to have multiple occurences of the same jar in several lib subdir, but i don't find other solution to have my build the less dependent from ivy ... 2007/3/26, Simon <[EMAIL PROTECTED]>:
Hello all, What is the best way to resolve the specific dependencies of a particular artifact into a path or fileset for use in Ant? For example, I have a war file (just one of the possible outputs from my project) which depends on A.jar, and A.jar depends on B.jar and C.jar. When I build my war file, I need to include those dependencies - it would be great if this could be completely computed from the ivy resolve process so that if the dependencies of A.jar change I won't need to change anything in the build for this project. I see there are two tasks that come close ( cachefileset and cachepath ) but they don't seem to match perfectly and also the docs recommend it's better not to use them .... so just wondering how everyone else is doing this? Thanks for any advice! Cheers, Simon.
