Return-Path: Delivered-To: apmail-incubator-ivy-user-archive@locus.apache.org Received: (qmail 75601 invoked from network); 14 Jan 2008 09:51:47 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 14 Jan 2008 09:51:47 -0000 Received: (qmail 98587 invoked by uid 500); 14 Jan 2008 09:51:36 -0000 Delivered-To: apmail-incubator-ivy-user-archive@incubator.apache.org Received: (qmail 98566 invoked by uid 500); 14 Jan 2008 09:51:36 -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 98557 invoked by uid 99); 14 Jan 2008 09:51:36 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Jan 2008 01:51:36 -0800 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of xavier.hanin@gmail.com designates 209.85.198.187 as permitted sender) Received: from [209.85.198.187] (HELO rv-out-0910.google.com) (209.85.198.187) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Jan 2008 09:51:11 +0000 Received: by rv-out-0910.google.com with SMTP id k20so1784864rvb.0 for ; Mon, 14 Jan 2008 01:51:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; bh=mjlfolv9LaE/GxxRfmhYSH8v8SqcCKvB6dXHVlK6spI=; b=SsBFxfbB9vzOoE/A9niE/y32R/wXv1ZdlKj25RqwimtcoIM8MPYPUifOAvlNBfjex3mgRVRxyV2RvqOe5qwqPzV69EOcXAAh4/ihnUQtevINKbhpiWls0ZP+MgwVA2a5Po5wtvyN+R/PWHuE/PPCtNbcRp8ZeZPGVrDHZghKQuw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=CxNSIeiKZs6woHfROZDyG5g9lvlz0CPRK2UPio1762ntHTKxIBXXm4LD9fk4J529NuT1nyXdXNAaNhjiqU12ngDATBvYNlE/r7KL89XsoZWHyqf7ky++7xXVbbd0MyIPHmM58jKMRwLzI84XTAPOimyXuIRX6KDC/6aMA1TXfrU= Received: by 10.141.99.4 with SMTP id b4mr3629067rvm.270.1200304276728; Mon, 14 Jan 2008 01:51:16 -0800 (PST) Received: by 10.141.171.19 with HTTP; Mon, 14 Jan 2008 01:51:16 -0800 (PST) Message-ID: <635a05060801140151p82c9c4j6d894b2f2b273d25@mail.gmail.com> Date: Mon, 14 Jan 2008 10:51:16 +0100 From: "Xavier Hanin" To: ivy-user@incubator.apache.org Subject: Re: Ivy internals question In-Reply-To: <15412A37E8C9574393B24ADD991FAA7608C5F7578A@MERCMBX14.na.sas.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_2479_25357631.1200304276722" References: <15412A37E8C9574393B24ADD991FAA7608C5F7578A@MERCMBX14.na.sas.com> X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_2479_25357631.1200304276722 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline On Jan 12, 2008 2:44 PM, Jim Adams wrote: > We have extended ivy somewhat at my company and are making calls directly > into 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 > resolving and then later publishing but, in between, I am asking to download > the latest integration version of the original ivy.xml file. What gets > published then includes revisions of latest.integrations instead of the > versions determined during the resolve. > > I am performing these calls to get the module. Then I parse it to get the > dependencies (non-transitive). I can then test those dependencies against > those from the resolve report. > > // go out and find what was resolved as latest.revision. This > returns what is out > // in the repo for this ivy.xml file > DependencyResolver resolver = settings.getResolver(id); > ResolvedModuleRevision _module = > resolver.getDependency(dependencyDescriptor, new ResolveData(resEngine, > rOpt, null )); > > My task is a IvyPostResolveTask so that I can get to the last resolve > report. Am I screwing up future uses of the last resolve report? No. The only task/operation changing this in memory representation is ResolveEngine#resolve. And even if you really need to call resolve, you can just use a different resolve ID, so there shouldn't be any problem. Xavier > > > > Jim Adams > Jim.Adams@sas.com > Principal Systems Developer > SAS Institute > > > -- Xavier Hanin - Independent Java Consultant http://xhab.blogspot.com/ http://ant.apache.org/ivy/ http://www.xoocode.org/ ------=_Part_2479_25357631.1200304276722--