We're recently changed many of our build systems to use Ivy/Artifactory and are generally pleased with the system. The major problem we have run into is that we can no longer checkout older (or tagged) revisions of Subversion repositories and be able to completely reproduce the build.
When JARs are checked into a SCM repository, the build is totally self-contained and you can revert back to any point in time that you need to. When you use a dependency server (like Artifactory), you lose this ability because some of the ivy.xml files may have tokens like "latest.integration" in them. Of course the latest integration versions available on the Artifactory server will be different between when the older build was created and what is currently available. And there's no good way to "revert" the Artifactory server back to the older/tagged state. Does anyone have ideas on how to handle this? thanks, Valerie ------------------------------------------------------------------------------ Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ Artifactory-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/artifactory-users
