This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
in standard version control management, when you release a product, you want to know everything you used to build the product + versions used.
our development group uses ivy to manage 3rd party and internally generated libs our products are dependent on. in many cases, the dependencies in the ivy.xml file for our products set "ref" to be "latest.integration".
if a product itself has artifacts it needs to publish, at the time of release, we'll publish the artifacts and in the ivy repository there will be a version of ivy.xml that for each dependency has "ref" values that reflect the actual version used for the 3rd party / internal lib.
if a product does not have artifacts, we don't have anything to publish and therefore don't get an ivy.xml that records the versions of each dependency used. ultimately, we could manually make a copy of the ivy.xml and go through each dependency and record what versions were used but we'd really like to automate it.
does anyone know how to do this? are we going about this the wrong way? we're relatively new to ivy. if you provide a suggestion, please be specific or include a link to the ivy documentation that shows us what do do.