From ivy-user-return-1763-apmail-incubator-ivy-user-archive=incubator.apache.org@incubator.apache.org Tue Oct 09 21:25:36 2007 Return-Path: Delivered-To: apmail-incubator-ivy-user-archive@locus.apache.org Received: (qmail 51061 invoked from network); 9 Oct 2007 21:25:35 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 9 Oct 2007 21:25:35 -0000 Received: (qmail 44191 invoked by uid 500); 9 Oct 2007 21:25:23 -0000 Delivered-To: apmail-incubator-ivy-user-archive@incubator.apache.org Received: (qmail 44171 invoked by uid 500); 9 Oct 2007 21:25:23 -0000 Mailing-List: contact ivy-user-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ivy-user@incubator.apache.org Delivered-To: mailing list ivy-user@incubator.apache.org Received: (qmail 44158 invoked by uid 99); 9 Oct 2007 21:25:23 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Oct 2007 14:25:23 -0700 X-ASF-Spam-Status: No, hits=-2.0 required=10.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy includes SPF record at spf.trusted-forwarder.org) Received: from [64.18.0.141] (HELO exprod5og101.obsmtp.com) (64.18.0.141) by apache.org (qpsmtpd/0.29) with SMTP; Tue, 09 Oct 2007 21:25:25 +0000 Received: from source ([69.48.200.224]) by exprod5ob101.postini.com ([64.18.4.12]) with SMTP; Tue, 09 Oct 2007 14:25:03 PDT Received: (qmail 3430 invoked by uid 509); 9 Oct 2007 16:25:03 -0500 Received: from 192.169.9.32 by sgp-ns-01.pointserve.com (envelope-from , uid 507) with qmail-scanner-1.25-st-qms (clamdscan: 0.87/3572. spamassassin: 3.1.9. perlscan: 1.25-st-qms. Clear:RC:1(192.169.9.32):. Processed in 0.16223 secs); 09 Oct 2007 21:25:03 -0000 X-Antivirus-MYDOMAIN-Mail-From: rloehr@pointserve.com via sgp-ns-01.pointserve.com X-Antivirus-MYDOMAIN: 1.25-st-qms (Clear:RC:1(192.169.9.32):. Processed in 0.16223 secs Process 3423) Received: from unknown (HELO PTSCORP-EXCH.pointserve.com) (192.169.9.32) by sgp-ns-01.pointserve.com with SMTP; 9 Oct 2007 16:25:02 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C80ABA.C6467827" Subject: setting up snapshots with ivy, not picking up latest snapshot Date: Tue, 9 Oct 2007 16:24:28 -0500 Message-ID: <43C7278FD7C46E42A193246BC2FEDA5C1B08D9@PTSCORP-EXCH.pointserve.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: setting up snapshots with ivy, not picking up latest snapshot Thread-Index: AcgKusXx1/voO2X6QZ234MD1G7xXmw== From: "Loehr, Ruel" To: X-Virus-Checked: Checked by ClamAV on apache.org ------_=_NextPart_001_01C80ABA.C6467827 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I'm trying to setup a snapshot system with ivy. My nightly build correctly publishes a jar with 1.0.0-SNAPSHOT version to my repository. =20 My build however, is not picking up the new snapshots and downloading the new version. =20 I'm calling : =20 1) ivy-setup (which just defines the ant tasks) 2) ivy-configure (shown below) 3) ivy-resolve 4) ivy-retrieve =20 =20 What is the expected behavior of resolve when determing when to download a new version of a version? When md5's change? When the timestamp changes? =20 =20 =20 =20 setup ivy configuration"> =20 =20 retreive = dependencies with ivy"> =20 =20 =20 =20 Ivyconf properties looks like this =20 ivy.conf.dir=3D${basedir}/config/ivy ivy.conf.file=3D${ivy.conf.dir}/ivyconf.xml ivy.ivyrep.default.ivy.root=3Dhttp://pts-bldwin-01/repository ivy.retrieve.pattern =3D ${basedir}/libs/[conf]/[artifact].[ext] =20 Ivy conf xml looks like this: =20 =20 =20 =20 =20 Ruel Loehr Configuration Management =20 Pointserve, Inc. 110 Wild Basin Road Suite 300 Austin, Texas 78746 O: 512.617.5314 F: 512.617.0466 =20 ------_=_NextPart_001_01C80ABA.C6467827--