Return-Path: Delivered-To: apmail-ant-ivy-user-archive@www.apache.org Received: (qmail 44827 invoked from network); 6 Feb 2008 20:47:15 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 6 Feb 2008 20:47:15 -0000 Received: (qmail 59177 invoked by uid 500); 6 Feb 2008 20:47:07 -0000 Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org Received: (qmail 59160 invoked by uid 500); 6 Feb 2008 20:47:07 -0000 Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ivy-user@ant.apache.org Delivered-To: mailing list ivy-user@ant.apache.org Received: (qmail 59151 invoked by uid 99); 6 Feb 2008 20:47:07 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Feb 2008 12:47:07 -0800 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of xavier.hanin@gmail.com designates 209.85.198.184 as permitted sender) Received: from [209.85.198.184] (HELO rv-out-0910.google.com) (209.85.198.184) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Feb 2008 20:46:38 +0000 Received: by rv-out-0910.google.com with SMTP id k15so2013271rvb.40 for ; Wed, 06 Feb 2008 12:46:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; bh=TsH59rawGKDBeMeGM/I1TJw9+QaEsiG6RX0txyJ7Amk=; b=MxCgjFwjEi8HS1NneTgelf89do/TrB0P6WvCRl6P88bO/lmFFKAKj6iaHurd/vFnqgjRZcPg5FYA40E1QUgdD/xcszFMCs00ctI0z9Il0eYPmlDEwVUrpVnxaVPJOTj1XQANkARHtnohRAY9O4zy5HfNazD52sVNVXPQfV1dhi8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=fZw8GuRwwIqPBcUPXH1W74in4SHvEmmbpqn6bN2eoA5SOKhF6Qq4mANGqdPkEuBPdEom+C1nG3h7hO7nWlECzRK2uWnEzzBSXtjG62DE2HS+JIDXgg08RhERUSn7GBbbx7QrkamO9YR85wO/P+eCCQv9at8PSxi42B/RPd5iAcQ= Received: by 10.141.142.15 with SMTP id u15mr1690783rvn.66.1202330804738; Wed, 06 Feb 2008 12:46:44 -0800 (PST) Received: by 10.140.225.10 with HTTP; Wed, 6 Feb 2008 12:46:44 -0800 (PST) Message-ID: <635a05060802061246v5216e826ob5b62f3919cfc141@mail.gmail.com> Date: Wed, 6 Feb 2008 21:46:44 +0100 From: "Xavier Hanin" To: ivy-user@ant.apache.org Subject: Re: cache problems In-Reply-To: <745B9EDF57802349B13F90E4E0B4B86C3B84EAEF24@HOUEXCH012.corp.halliburton.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_17544_10651150.1202330804709" References: <745B9EDF57802349B13F90E4E0B4B86C3B84EAEF23@HOUEXCH012.corp.halliburton.com> <635a05060802052348k449e1ac5kd8c7bf71a9d46a1b@mail.gmail.com> <745B9EDF57802349B13F90E4E0B4B86C3B84EAEF24@HOUEXCH012.corp.halliburton.com> X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_17544_10651150.1202330804709 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline On Feb 6, 2008 4:26 PM, Shawn Castrianni wrote: > In order to have globally unique rev numbers, I would need to put things > like branch and status into the rev number. How do I do that? what you can do is use the ivy:info task to load metadata from your ivy file and use this data to call buildnumber. Xavier > I already tried using [branch] and [status] in the pubrevision attribute > on my publish task, but they don't get resolved. I am currently calling > ivy's buildnumber task so that I can format my rev numbers like yyMMdd.#: > > > > > revision="${dateStamp}."/> > > Do I put the [branch] and [status] in the buildnumber call, maybe? > > --- > Shawn Castrianni > CM Lead Architect > Landmark > Halliburton Drilling, Evaluation and Digital Solutions Building 2 > 2101 City West Blvd. > Houston, TX 77042 > Work: 713-839-3086 > Cell: 832-654-0888 > Fax: 713-839-2758 > > -----Original Message----- > From: Xavier Hanin [mailto:xavier.hanin@gmail.com] > Sent: Wednesday, February 06, 2008 1:49 AM > To: ivy-user@ant.apache.org > Subject: Re: cache problems > > On Feb 6, 2008 8:25 AM, Shawn Castrianni > > wrote: > > > How important is the cache? All of my work is within my corporate > > intranet so everything is pretty fast. The reason I ask is that the > cache > > seems to cause me headache. I am testing different scenarios and > features > > of ivy with test build.xml and ivy.xml files. When I think my ivy file > > should fail in finding a module during retrieve, it succeeds because it > > found the wrong one in the cache. If I delete my cache and then rerun > my > > test, it fails as I expect. That makes me think that when I deploy my > ivy > > implementation, my users will sometimes be picking up the wrong > dependencies > > because of stuff in the cache. Am I doing something wrong? I am > thinking I > > should do a cleancache before every ivy task to make sure it is clean > for > > each of my ivy tasks. Can I just turn off the usage of the cache? > > Obviously, this is not the intended behavior of someone using ivy so I > must > > be missing something. > > Ivy 2 cache management has been highly improved, but you can't disable the > cache completely, since all post resolve tasks rely on file only, so > resolve > need to ensure that all your dependencies are available as files. If > you're > working with a fast enough shared file system, you can just set > useOrigin="true" on your cache settings, and you'll almost disable the > cache > (we still have some issues to fix with the new cache implementation, but > it > should already work pretty fine). If you use ofther kind of resolvers > (http, > ...) then Ivy we'll need to download files in the cache. So what you can > do > is either clean your cache before each run, or set checkModified="true" > and > changingPattern="*" to make sure Ivy will always look at your repository. > > On the other hand, I still think having unique revisions is a good > practice, > and if you follow this principle you won't ever have any problem with the > cache. > > > > > > > My module revision numbers are not globally unique. I could have a > > revision 080205.00 for module A branch 1 and a revision 080205.00 for > > module A branch 2. If the cache is just looking at the revision numbers > > assuming they are globally unique, then it could sometimes get the wrong > > branch version since the revision numbers are the same. Is this a bug > in > > the cache or do I need to make my revision numbers globally unique by > adding > > the branch name somehow? > > Antoine has just raised an issue about the exact same problem which still > needs to be better qualified. As Maarten suggests in the issue, the cause > may only be that Ivy doesn't currently use the branch token in the default > cache patterns. This can easily be fixed, I suggest trying it out. > > Xavier > > > > > > > > --- > > Shawn Castrianni > > Landmark > > Halliburton Drilling, Evaluation and Digital Solutions > > Building 2 > > 2101 City West Blvd. > > Houston, TX 77042 > > Work: 713-839-3086 > > Cell: 832-654-0888 > > Fax: 713-839-2758 > > > > ---------------------------------------------------------------------- > > This e-mail, including any attached files, may contain confidential and > > privileged information for the sole use of the intended recipient. Any > > review, use, distribution, or disclosure by others is strictly > prohibited. > > If you are not the intended recipient (or authorized to receive > information > > for the intended recipient), please contact the sender by reply e-mail > and > > delete all copies of this message. > > > > > -- > Xavier Hanin - Independent Java Consultant > http://xhab.blogspot.com/ > http://ant.apache.org/ivy/ > http://www.xoocode.org/ > -- Xavier Hanin - Independent Java Consultant http://xhab.blogspot.com/ http://ant.apache.org/ivy/ http://www.xoocode.org/ ------=_Part_17544_10651150.1202330804709--