I’ve been going through some of the Ivy code recently and have a few related questions. Some of my basic testing shows that a “resolve” of a module produces the following (internal) files:
1. A resolution report, in the form of XML, per configuration of the module, in the form of <org>-<module>-<conf>.xml (ex: foo-bar-conf1.xml) and consists a comprehensive detail about the (dependency) resolution of that module including where the artifacts reside etc… 2. A XML file called resolved-<org>-<module>-<version>.xml (ex: resolved-foo-bar-1.0.xml) which essentially is a ivy.xml of the module. This is similar to the file that resides in the Ivy cache for that module. 3. A properties file of the form resolved-<org>-<module>-<version>.properties (ex: resolved-foo-bar-1.0.properties). I see that the properties file does get used in some places, but haven’t fully grasped the details about it. When is it really used and what exact role does it play? Same question with the XML file in #2. From what I see the resolution report per configuration of the module (the #1) has all the necessary information about the resolution. Would it not be enough for any kind of post-resolution activities? In other words, internally, can it be used exclusively (as a single source of truth) without the need of the files in #2 and #3? -Jaikiran --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
