Return-Path: Delivered-To: apmail-ant-notifications-archive@minotaur.apache.org Received: (qmail 44599 invoked from network); 31 Aug 2009 18:01:57 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 31 Aug 2009 18:01:57 -0000 Received: (qmail 65459 invoked by uid 500); 31 Aug 2009 18:01:57 -0000 Delivered-To: apmail-ant-notifications-archive@ant.apache.org Received: (qmail 65397 invoked by uid 500); 31 Aug 2009 18:01:57 -0000 Mailing-List: contact notifications-help@ant.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ant.apache.org Delivered-To: mailing list notifications@ant.apache.org Received: (qmail 65388 invoked by uid 99); 31 Aug 2009 18:01:56 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 31 Aug 2009 18:01:56 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 31 Aug 2009 18:01:54 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id E302D234C1EC for ; Mon, 31 Aug 2009 11:01:32 -0700 (PDT) Message-ID: <300698973.1251741692928.JavaMail.jira@brutus> Date: Mon, 31 Aug 2009 11:01:32 -0700 (PDT) From: "Carlton Brown (JIRA)" To: notifications@ant.apache.org Subject: [jira] Commented: (IVY-938) Fixed name snapshots are not updated even if they are marked as changing and the publication date is changed in repo In-Reply-To: <2141174062.1223627744509.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/IVY-938?page=3Dcom.atlassian.ji= ra.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1274955= 6#action_12749556 ]=20 Carlton Brown commented on IVY-938: ----------------------------------- I have not been able to get this working with the trunk revision. In fact= I found that the behavior is a race condition when the latest-time strateg= y is used on both the subresolvers in the chain. =20 Question - When Ivy is iterating a chain, and it finds 2 instances of the s= ame module/revision in different subresolvers, what is the expected behavio= r? Can Ivy use latest-time to decide which is latest? Or is it incapable= of evaluating these as distinct revisoins? > Fixed name snapshots are not updated even if they are marked as changing = and the publication date is changed in repo > -------------------------------------------------------------------------= ------------------------------------------- > > Key: IVY-938 > URL: https://issues.apache.org/jira/browse/IVY-938 > Project: Ivy > Issue Type: Bug > Components: Core, Maven Compatibility > Affects Versions: 2.0-RC1 > Reporter: Jyri Kyt=C3=B6m=C3=A4ki > Attachments: CacheUpdateTest.zip, CacheUpdateTest2.zip, ivysettin= gs.xml > > > Snapshot releases with static name like 1.2.3-SNAPSHOT are not updated in= to the cache. > Same problem is with ivy and maven remote repos. > Here ivy example: > Remote ivy repo contains in ivy xml: > status=3D"integration" publication=3D"20081010104634" > Cache contains (.xml): > status=3D"integration" publication=3D"20081010095107" > But ivy_resolve does not update the cache. It prints this with verbose o= utput: > [ivy-resolve] default: Checking cache for: dependency: org#>module;1.2.3-= SNAPSHOT {runtime=3D[runtime]} > [ivy-resolve] don't use cache for org#>module;1.2.3-SNAPSHOT: changing=3D= true > [ivy-resolve] local: Checking cache for: dependency: org#>module;1.2.3-SN= APSHOT{runtime=3D[runtime]} > [ivy-resolve] local: module revision found in cache: org#>module;1.2.3-SN= APSHOT > [ivy-resolve] found org#>module;1.2.3-SNAPSHOT in remote_ivy > ... > [ivy-resolve] :: downloading artifacts :: > [ivy-resolve] [NOT REQUIRED] org#>module;1.2.3-SNAPSHOT!module.jar --=20 This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.