ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xavier Hanin" <>
Subject Re: Ivy internals question
Date Mon, 14 Jan 2008 09:51:16 GMT
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.


> Jim Adams
> Principal Systems Developer
> SAS Institute

Xavier Hanin - Independent Java Consultant

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message