From ivy-user-return-2294-apmail-incubator-ivy-user-archive=incubator.apache.org@incubator.apache.org Sat Jan 12 13:44:57 2008 Return-Path: Delivered-To: apmail-incubator-ivy-user-archive@locus.apache.org Received: (qmail 7865 invoked from network); 12 Jan 2008 13:44:57 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 12 Jan 2008 13:44:57 -0000 Received: (qmail 86578 invoked by uid 500); 12 Jan 2008 13:44:46 -0000 Delivered-To: apmail-incubator-ivy-user-archive@incubator.apache.org Received: (qmail 86549 invoked by uid 500); 12 Jan 2008 13:44:46 -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 86537 invoked by uid 99); 12 Jan 2008 13:44:46 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 12 Jan 2008 05:44:46 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of Jim.Adams@sas.com designates 149.173.6.153 as permitted sender) Received: from [149.173.6.153] (HELO mercav06.na.sas.com) (149.173.6.153) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 12 Jan 2008 13:44:22 +0000 Received: from merchub01.na.sas.com ([10.19.20.24]) by mercav06.na.sas.com with InterScan Message Security Suite; Sat, 12 Jan 2008 08:44:26 -0500 Received: from MERCMBX14.na.sas.com ([10.19.20.114]) by merchub01.na.sas.com ([10.19.20.24]) with mapi; Sat, 12 Jan 2008 08:44:26 -0500 From: Jim Adams To: "ivy-user@incubator.apache.org" Date: Sat, 12 Jan 2008 08:44:24 -0500 Subject: Ivy internals question Thread-Topic: Ivy internals question Thread-Index: AchVIT4BKabZ2u5rRcatQ6IQrXgpgw== Message-ID: <15412A37E8C9574393B24ADD991FAA7608C5F7578A@MERCMBX14.na.sas.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org We have extended ivy somewhat at my company and are making calls directly i= nto the ivy API at times. The question is: What operations will ruin the in= -memory representation of a resolve? What I am seeing is that I am resolvin= g and then later publishing but, in between, I am asking to download the la= test integration version of the original ivy.xml file. What gets published = then includes revisions of latest.integrations instead of the versions dete= rmined during the resolve. I am performing these calls to get the module. Then I parse it to get the d= ependencies (non-transitive). I can then test those dependencies against th= ose from the resolve report. // go out and find what was resolved as latest.revision. This r= eturns what is out // in the repo for this ivy.xml file DependencyResolver resolver =3D settings.getResolver(id); ResolvedModuleRevision _module =3D resolver.getDepe= ndency(dependencyDescriptor, new ResolveData(resEngine, rOpt, null )); My task is a IvyPostResolveTask so that I can get to the last resolve repor= t. Am I screwing up future uses of the last resolve report? Jim Adams Jim.Adams@sas.com Principal Systems Developer SAS Institute