Return-Path: Delivered-To: apmail-ant-ivy-user-archive@www.apache.org Received: (qmail 51893 invoked from network); 16 Jul 2010 09:25:22 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 16 Jul 2010 09:25:22 -0000 Received: (qmail 35213 invoked by uid 500); 16 Jul 2010 09:25:22 -0000 Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org Received: (qmail 34986 invoked by uid 500); 16 Jul 2010 09:25:19 -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 34977 invoked by uid 99); 16 Jul 2010 09:25:18 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Jul 2010 09:25:18 +0000 X-ASF-Spam-Status: No, hits=2.9 required=10.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_HELO_PASS,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [212.227.126.186] (HELO moutng.kundenserver.de) (212.227.126.186) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Jul 2010 09:25:10 +0000 Received: from mail-ew0-f45.google.com (mail-ew0-f45.google.com [209.85.215.45]) by mrelayeu.kundenserver.de (node=mrbap0) with ESMTP (Nemesis) id 0LnDv3-1PH1fb00Ev-00h3re; Fri, 16 Jul 2010 11:24:50 +0200 Received: by ewy5 with SMTP id 5so661183ewy.4 for ; Fri, 16 Jul 2010 02:24:47 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.173.2 with SMTP id u2mr538838wel.56.1279272287439; Fri, 16 Jul 2010 02:24:47 -0700 (PDT) Received: by 10.216.138.94 with HTTP; Fri, 16 Jul 2010 02:24:47 -0700 (PDT) In-Reply-To: References: <812857.80297.qm@web30802.mail.mud.yahoo.com> Date: Fri, 16 Jul 2010 11:24:47 +0200 Message-ID: Subject: Re: Update policy for Maven snapshots From: Hans Dockter To: ivy-user@ant.apache.org Content-Type: multipart/alternative; boundary=0016e64f7e4d4394c7048b7dca07 X-Provags-ID: V02:K0:V8s9D7aKfgbNgqdsISCPwM66kp6FRUDikCHbAMssVO7 B/h5GF8Xs2+o7C6Txdk6jHFB9pzQ5wo5tLpkM3XbAwyF/qmwcP gAZ26+Zgvlaru6O+LGCg98ZR7hh4Z/vQO4QeILaFcoPRLlP3qX x8Nt86FLGQrs9kMe4ZZW07WEtk8IhDQeeLMphKrj83JB1rwTnv cVS08MuA+KuaIC1DVHlE4SB7wRlgS06zUfWrqBgouY= X-Virus-Checked: Checked by ClamAV on apache.org --0016e64f7e4d4394c7048b7dca07 Content-Type: text/plain; charset=ISO-8859-1 I think always doing a remote check for Maven snapshots is a critical problem for any Ivy user working with Maven snapshot repositories. It can slow down the build to a point were it is basically unusable when you have many snapshots. I have tried to add a custom VersionMatcher for Maven snapshots that considers .*-SNAPSHOT as dynamic. Then I run into the issues that dynamic version names must be transformed before a resolve. Otherwise Ivy throws an exception. In that case that requirement doesn't seem to be necessary. It looks like a blocker for an easy solution via VersionMatchers that work with the current IBiblioResolver. The solution I have implemented is to have a custom version of the IBiblioResolver which overwrites the findModuleInCache method. Although this works, I think a solution that integrates into the very nice generic dynamic version handling of Ivy would be much better. I will file a Jira. - Hans -- Hans Dockter Founder, Gradle http://www.gradle.org, http://twitter.com/gradleorg CEO, Gradle Inc. - Gradle Training, Support, Consulting http://www.gradle.biz --0016e64f7e4d4394c7048b7dca07--