Hello, I'm looking for help with resolving dependencies for tools found in a build file but that are not dependencies for the project being built.
My company has started a strong effort to migrating our builds to incorporate ivy mostly for dependency management as part of getting control on an otherwise unwieldy collection of build.xmls. We've made good progress but many details remain. One detail is how to resolve the dependencies of tools that are required in the build itself. We have a build.xml that is included in a number of other projects (build-tools.xml) and some in-house tools that are invoked by targets in the build-tools.xml. The jars required for these tools are not required by the projects being built but they are required for these targets to perform specific actions. I could refer to the jars statically, as we already do, but part of this effort is to move away from doing that. It seems that what we need is an ivy.xml just for these tools that is separate from the ivy.xml of the project that is being compiled. Any help here? Thank you, -Ben -- Benjamin Damm Silver Spring Networks 650-298-4200 x201
