One problem I ran into while using this mechanism is that if the dependency is based on a "latest.integration" revision and the ivy.xml pattern for the repository does not have the revision number somewhere in it, this mechanism will fail.
The other possibility is that your test sequence may need to be changed slightly. You may have to change ivysettings.xml first. Lastly, maybe it was simply not working well in RC2. That's all I can think of. Scott -----Original Message----- From: Mike Quilleash [mailto:[email protected]] Sent: Thursday, May 13, 2010 12:31 PM To: [email protected] Subject: RE: Refreshing ivy cache after changing a published version Thanks. I tried doing the following to test.. - Cleaned out my ivy cache and cleaned my project build - Removed one of the jar entries from one ivy.xml in my repository - Did a build - Dependencies were downloaded, build failed because of missing jar - Edited the ivy.xml in the repository to put the jar reference back in - Changed the resolver in the project ivysettings.xml with checkmodified and changingPattern like below <filesystem name="shared" checkmodified="true" changingPattern=".*"> - Reran build - Still failed. The additional jar was not downloaded. What am I missing? -----Original Message----- From: Scott Goldstein [mailto:[email protected]] Sent: 13 May 2010 18:04 To: [email protected] Subject: RE: Refreshing ivy cache after changing a published version Take a look at the Cache Management section on the main concepts page: http://ant.apache.org/ivy/history/latest-milestone/concept.html Specifically, look at the subsection entitled "Change Management". Scott -----Original Message----- From: Mike Quilleash [mailto:[email protected]] Sent: Thursday, May 13, 2010 7:59 AM To: [email protected] Subject: Refreshing ivy cache after changing a published version Hi all, I have an Ivy repository where we store all our 3rd party libraries. One of these is a large C# UI component library that comprises 100+ DLLs. In reality we only need about 10-15 of those DLLs but we sometimes need additional ones added as we use new functionality. This isn't a version change as the version of the library we use doesn't change, we just add additional DLLs to an existing version. If I just drop the relevant DLLs in the repository area and update the relevant ivy.xml. But then when I try to build a project which depends on these new DLLs it fails because it doesn't realise I have changed the contents of an existing version (that version will already be in the local ivy cache) so it doesn't download the new files from the repository. Is there any setting/command I can use to force Ivy to do a check of the ivy.xml descriptors in the repository and, if anything has changed, refresh that library. We can do a clean of the ivy cache but it's a bit painful for developers who connect over the VPN, can take quite a while to re-downloaded everything. I'm using ant 1.7.1 and ivy 2.1.0RC2. Any suggestions appreciated. Cheers. Mike. ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. ______________________________________________________________________ - -------------------------------------------------------------------- STATEMENT OF CONFIDENTIALITY The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain confidential or privileged information. No representation is made on its accuracy or completeness of the information contained in this electronic message. Certain assumptions may have been made in the preparation of this material as at this date, and are subject to change without notice. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail and any attachment(s) is strictly prohibited. Please reply to the sender at NextLabs Inc and destroy all copies of this message and any attachments from your system. ====================================================================== ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. ______________________________________________________________________ - -------------------------------------------------------------------- STATEMENT OF CONFIDENTIALITY The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain confidential or privileged information. No representation is made on its accuracy or completeness of the information contained in this electronic message. Certain assumptions may have been made in the preparation of this material as at this date, and are subject to change without notice. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail and any attachment(s) is strictly prohibited. Please reply to the sender at NextLabs Inc and destroy all copies of this message and any attachments from your system. ======================================================================
