Return-Path: Delivered-To: apmail-ant-ivy-user-archive@www.apache.org Received: (qmail 7740 invoked from network); 31 Aug 2009 02:52:49 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 31 Aug 2009 02:52:49 -0000 Received: (qmail 62174 invoked by uid 500); 31 Aug 2009 02:52:48 -0000 Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org Received: (qmail 62105 invoked by uid 500); 31 Aug 2009 02:52:48 -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 62095 invoked by uid 99); 31 Aug 2009 02:52:48 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 31 Aug 2009 02:52:48 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of mgitman@gmail.com designates 209.85.218.212 as permitted sender) Received: from [209.85.218.212] (HELO mail-bw0-f212.google.com) (209.85.218.212) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 31 Aug 2009 02:52:40 +0000 Received: by bwz8 with SMTP id 8so2038349bwz.28 for ; Sun, 30 Aug 2009 19:52:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=O9dq7DuKOIws3OKhRIw8QS8KJ2s1Q0aeNrilFJoMig0=; b=d933eZDgbvYKY2H+EXx3Sjrlf5nCRBXhzXuKhj34exeS0fXC098sfmAornvTL6qgps /69k5Z94+y6EApYdHv4DYM+Nf/fb3M2UazhSufx2oCnxdS3ZsnPyoI8+9ygVDuFUWGvy wHdtROMC0wS0LiasTrpK9So1ADwHfz0eiIfkE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=cQ5YNsdS/pWI1Iu4QBz+72HECc4hba38I8t0YNkjdtop6iIpTskaswbB51Td9o8HyD Ikk0RYCw7jnEnbnWxLzeC2JyN/H2/TgTWftwk2DjuX4JH+jUlyYJ+zr8Fl9hCDyHrAW0 ct1p50TeAiMoN3E9DUr8xgqMdb2bRseeff+/A= MIME-Version: 1.0 Received: by 10.223.143.79 with SMTP id t15mr1433600fau.26.1251687138904; Sun, 30 Aug 2009 19:52:18 -0700 (PDT) In-Reply-To: <6B4D8A42E536AC4EAC179B77DC162AB2792F02@atl-mail03.corp.int-silverpop.com> References: <6B4D8A42E536AC4EAC179B77DC162AB2792F02@atl-mail03.corp.int-silverpop.com> Date: Sun, 30 Aug 2009 19:52:18 -0700 Message-ID: <7916a6a60908301952h5e15e09cj2f493ae16b2d5c0a@mail.gmail.com> Subject: Re: checkModified and changing pattern From: Mitch Gitman To: ivy-user@ant.apache.org Content-Type: multipart/alternative; boundary=0023545bda2848c9a80472671f60 X-Virus-Checked: Checked by ClamAV on apache.org --0023545bda2848c9a80472671f60 Content-Type: text/plain; charset=UTF-8 Carlton, since no one else has gotten back yet on your question, I would ask you, why not just run an experiment and see if changingPattern behaves any differently with or without lastmodified="true"? Actually, I'd be curious myself. The documentation is ambiguous on this score. My intuition says: - A changingPattern in combination with lastmodified="true" means, even if the repository ivy.xml file is newer than the cached one, don't download the module unless the revision also matches the pattern. - A changingPattern in combination with lastmodified="false" means, always download the module if the revision value matches the pattern; don't even bother checking the timestamp on the ivy.xml (if there even is an ivy.xml). Well, that's what my intuition says, but my intuition has been wrong before. The only value I can see in the second scenario above (if it even exists) is if there is no ivy.xml. If there is an ivy.xml, then if the artifacts have been updated, the ivy.xml will have been updated too via ivy:publish. On Wed, Aug 26, 2009 at 12:20 PM, Carlton Brown wrote: > Question - > > > > According to the documentation, if you wish to use a snapshot strategy, > it's necessary to specify a changingPattern for the resolver (or define > the dependency as changing). This is very clear. > > > > Elsewhere in the documentation it is also suggested that this must be > used together with the checkModified pattern, but it doesn't exactly say > why. What would be the expected result of using a changingPattern > without checkModified? I don't understand the interplay between these > two attributes or why they must be specified separately. > > > > Thanks, > > Carlton > > > > ***CONFIDENTIALITY NOTICE and DISCLAIMER*** > This message and any attachment are confidential and may be > privileged or otherwise protected from disclosure and solely for > the use of the person(s) or entity to whom it is intended. If you > have received this message in error and are not the intended > recipient, please notify the sender immediately and delete this > message and any attachment from your system. If you are not the > intended recipient, be advised that any use of this message is > prohibited and may be unlawful, and you must not copy this > message or attachment or disclose the contents to any other person. --0023545bda2848c9a80472671f60--