Yes, I did clean the cache. Just out of clarity here is how I'm testing it :
1. delete cache: rm -rf /etc/ivy/cache/ 2. running the comand to download for the first time the jars : /usr/bin/java -Divy.default.ivy.user.dir=/etc/ivy/ -jar /usr/share/java/ivy.jar -settings /etc/ivy/ivy-settings.xml -ivy /etc/ivy/ivy.xml 3. I published again the jars (same jars, but timestamp change on the nexus server) 4. run commands again. I'm wondering if a new download would be trigger if the checksum of the jar changed. Maybe I need to actually change something in the code for Ivy to download it again ? ps2hekmat: nicely spotted ;) , I added the missing '.' but it does not change current behavior. On 14 January 2011 17:38, Hekmat, Payam <phek...@onenetwork.com> wrote: > I could be mistaken, but shouldn't the changingPattern be ".*-SNAPSHOT" for > a regexp matcher (or "*-SNAPSHOT" for glob)? > > -----Original Message----- > From: Mitch Gitman [mailto:mgit...@gmail.com] > Sent: Friday, January 14, 2011 10:36 AM > To: ivy-user@ant.apache.org > Subject: Re: Downloading new snapshot (trigger by timestamp) > > No, I mean clean the Ivy cache just this once so that the new settings have > an opportunity to be recognized. > > On Fri, Jan 14, 2011 at 8:33 AM, Romain Pelisse <bela...@gmail.com> wrote: > > > Hi, > > > > Yes, but I would like to avoid cleaning the cache everytime. This idea is > > that Ivy just checks if some of the content of the cache has actually > > changed on the nexus repository. If I clean the cache everytime, I'll end > > up > > download everything, everytime. > > > > I just tried adding checkmodified="true" on my resolver : > > > > <url name="my-resolver" > > changingPattern="\*-SNAPSHOT" > > changingMatcher="regexp" > > checkmodified="true" > > m2compatible="true"> > > > > But sadly, as you suspected, Ivy does not treats pom.xml like ivy.xml in > > this regards... > > > > > > On 14 January 2011 17:21, Mitch Gitman <mgit...@gmail.com> wrote: > > > > > First try clearing out your Ivy cache either with the ivy:cleancache > task > > > or > > > manually, and then try again. > > > > > > One alternative is to specify checkmodified="true". That's presuming > that > > > every time you publish a new snapshot, you're publishing the new pom > with > > > it. I'm assuming that checkmodified="true" treats a pom.xml like an > > > ivy.xml, > > > but I don't know that for a fact. > > > > > > On Fri, Jan 14, 2011 at 7:47 AM, Romain Pelisse <bela...@gmail.com> > > wrote: > > > > > > > Hi Mitch, > > > > > > > > Thanks for your reply, I quickly tried it, but it does not seems to > > > trigger > > > > a new download when the snapshot change on Nexus. (the jars keep the > > same > > > > name and the same version, SNAPSHOT, but the timestamp change). > > > > > > > > Here is my settings: > > > > > > > > <url name="my-resolver" > > > > changingPattern="\*-SNAPSHOT" > > > > changingMatcher="regexp" > > > > m2compatible="true"> > > > > ... > > > > > > > > Did I miss something here or ? > > > > > > > > Also, you mentions there would be several way to do so, would mind > > > > elaborate > > > > (quickly) ? I think it would help me have a better grasp of Ivy (at > > least > > > > regarding how I use it). > > > > > > > > Thanks ! > > > > > > > -- Romain PELISSE, *"The trouble with having an open mind, of course, is that people will insist on coming along and trying to put things in it" -- Terry Pratchett* http://belaran.eu/wordpress/belaran
