From notifications-return-8714-apmail-ant-notifications-archive=ant.apache.org@ant.apache.org Wed Jul 01 22:51:03 2009 Return-Path: Delivered-To: apmail-ant-notifications-archive@minotaur.apache.org Received: (qmail 20283 invoked from network); 1 Jul 2009 22:51:01 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 1 Jul 2009 22:51:01 -0000 Received: (qmail 35396 invoked by uid 500); 1 Jul 2009 22:51:11 -0000 Delivered-To: apmail-ant-notifications-archive@ant.apache.org Received: (qmail 35345 invoked by uid 500); 1 Jul 2009 22:51:11 -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 35335 invoked by uid 99); 1 Jul 2009 22:51:11 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Jul 2009 22:51:11 +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; Wed, 01 Jul 2009 22:51:08 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 6AE5A234C044 for ; Wed, 1 Jul 2009 15:50:47 -0700 (PDT) Message-ID: <1994240689.1246488647436.JavaMail.jira@brutus> Date: Wed, 1 Jul 2009 15:50:47 -0700 (PDT) From: "Maarten Coene (JIRA)" To: notifications@ant.apache.org Subject: [jira] Updated: (IVY-1085) Retrieve ant task doesn't support dynamic resolve mode In-Reply-To: <506183618.1243456665556.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-1085?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:all-tabpanel ] Maarten Coene updated IVY-1085: ------------------------------- Affects Version/s: (was: 2.1.0) Fix Version/s: 2.1.0-RC2 Assignee: Maarten Coene Issue Type: Improvement (was: Bug) Summary: Retrieve ant task doesn't support dynamic resolve mo= de (was: Retrieve ant task doesn't respect dynamic revisions for transitiv= e dependencies) > Retrieve ant task doesn't support dynamic resolve mode > ------------------------------------------------------ > > Key: IVY-1085 > URL: https://issues.apache.org/jira/browse/IVY-1085 > Project: Ivy > Issue Type: Improvement > Components: Ant > Affects Versions: 2.0.x, trunk > Reporter: Jaros=C5=82aw Wypychowski > Assignee: Maarten Coene > Fix For: 2.1.0-RC2 > > > let's have modules A, B and C. A depends on B which depends on C. > I have following versions released :=20 > - A - none, depends on B : 0.0.+ > - B - 0.0.1 , depends on C : 0.0.+, released with C rev=3D0.0.1, > - C - 0.0.1 and 0.0.2 > In order to always use freshest released version matching constraints I t= ried to use resolveMode=3D"dynamic" in resolve task. This worked for resolv= e (report shows correct dependency choosen (C:0.0.2). However retrieve happ= ily ignores it and downloads 0.0.1. I'm resolving with resolveId and retrie= ving with the same resolveId. > I tracked this a little bit. > Inside IvyPostResolveTask there is prepareAndCheck method. It does some m= agic which gets down to that ivy in most scenarios (when retrieval is not i= nline for known module and organisation) does a second resolve inside retri= eve to get configurations for retrieval. This is done in ensureResolve meth= od: > {code:java} > protected void ensureResolved(IvySettings settings) { > String requestedConfigs =3D getProperty(getConf(), settings, "ivy= .resolved.configurations"); > =20 > String[] confs =3D null; > if (getResolveId() !=3D null) { > confs =3D getConfsToResolve(getResolveId(), requestedConfigs)= ; > } else { > confs =3D getConfsToResolve(getOrganisation(), getModule(), r= equestedConfigs, false); > } > =20 > if (confs.length > 0) { > IvyResolve resolve =3D createResolve(isHaltonfailure(), isUse= Origin()); > resolve.setFile(getFile()); > resolve.setTransitive(isTransitive()); > resolve.setConf(StringUtils.join(confs, ", ")); > resolve.setResolveId(getResolveId()); > resolve.execute(); > } > } > {code} > First - could someone please rationalise this resolve inside retrieve ? = =20 > Second - this resolve happily ignores whatever resolveMode I did set prev= iously.=20 > The workaround I did was to extend IvyPostResolveTask with resolveMode pa= rameter and put it explicitly in to the ant config, but maybe there is a be= tter solution ?=20 > If the above is accepted I can produce a patch against trunk and post it = here.=20 --=20 This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.