Return-Path: Delivered-To: apmail-ant-notifications-archive@minotaur.apache.org Received: (qmail 10129 invoked from network); 4 Aug 2009 19:08:32 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 4 Aug 2009 19:08:32 -0000 Received: (qmail 1816 invoked by uid 500); 4 Aug 2009 19:08:37 -0000 Delivered-To: apmail-ant-notifications-archive@ant.apache.org Received: (qmail 1783 invoked by uid 500); 4 Aug 2009 19:08:37 -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 1774 invoked by uid 99); 4 Aug 2009 19:08:37 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Aug 2009 19:08:37 +0000 X-ASF-Spam-Status: No, hits=-1998.5 required=10.0 tests=ALL_TRUSTED,WEIRD_PORT 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; Tue, 04 Aug 2009 19:08:35 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id E16F929A0020 for ; Tue, 4 Aug 2009 12:08:14 -0700 (PDT) Message-ID: <1023891465.1249412894922.JavaMail.jira@brutus> Date: Tue, 4 Aug 2009 12:08:14 -0700 (PDT) From: "Paul Andrews (JIRA)" To: notifications@ant.apache.org Subject: [jira] Issue Comment Edited: (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=3D1273909= 5#action_12739095 ]=20 Paul Andrews edited comment on IVY-938 at 8/4/09 12:07 PM: ----------------------------------------------------------- The file is being served by hudson directly. The configuration I use is as = follows: =09 =09 =09=09 =09 =09 =09=09 =09=09=09 =09=09=09 =09=09=09 =09=09=09 =09=09=09=09 =09=09=09 =09=09 =09 The snapshot artifact is not in the "internal" repository, it is in "hudson= _sper". I have traced the TCP traffic to both repositories and Ivy only iss= ues one request: an HTTP HEAD request for the artifact itself. At no time d= oes it attempt to retrieve an ivy file. The server returns a modification d= ate later than the modification date of any copy of the artifact on my loca= l machine - either in the ivy cache or in the location that the artifact is= copied to by the resolver. I don't see much point 'publishing' an ivy file to hudson_sper, since Ivy m= akes no attempt to access one anyway. BTW I have tried several variations of the above settings file (for example= removing the stanza, not specifying the matcher etc. T= he results are the same. was (Author: mpandrews): The file is being served by hudson directly. The configuration I use is= as follows: =09 =09 =09=09 =09 =09 =09=09 =09=09=09 =09=09=09 =09=09=09 =09=09=09 =09=09=09=09 =09=09=09 =09=09 =09 The snapshot artifact is not in the "internal" repository, it is in "hudson= _sper". I have traced the TCP traffic to both repositories and Ivy only iss= ues one request: an HTTP HEAD request for the artifact itself. At no time d= oes it attempt to retrieve an ivy file. The server returns a modification d= ate later than the modification date of any copy of the artifact on my loca= l machine - either in the ivy cache or in the location that the artifact is= copied to by the resolver. I don't see much point 'publishing' an ivy file to hudson_sper, since Ivy m= akes no attempt to access one anyway. =20 > 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.