ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Archie Cobbs <>
Subject Re: inline resolve mode
Date Tue, 23 Jun 2009 17:33:05 GMT
FWIW, the way I would do this is create an XSLT that takes "A,B" as the
parameter and adds the dependencies to the normal ivy.xml. Then in your
build file, generate this new temporary ivy.xml via the <xslt> task and use
it instead for your resolution.


On Tue, Jun 23, 2009 at 11:18 AM, Shawn Castrianni <> wrote:

> I am trying to allow my users to experiment with dependencies.  I do have
> real ivy.xml files for all of my modules.  Right now, if my users want to
> experiment and change their dependencies of their module, they have to edit
> the dependencies section of the ivy.xml file.  That is fine, however, by
> changing the real ivy.xml file, they may accidentally commit this change to
> the SVN repo by mistake.  Therefore, I would like to somehow give them a way
> to add dependencies to the ones already listed in the ivy.xml file through
> some ANT property or something.  Like:
> ant dependencies -DextraDependencies="A,B"
> my ant script could check if the extraDependencies property is set and then
> somehow tell ivy to add these two modules (A and B) to the list of
> dependencies found in the ivy.xml file
> ---
> Shawn Castrianni
> -----Original Message-----
> From: Archie Cobbs []
> Sent: Tuesday, June 23, 2009 9:41 AM
> To:
> Subject: Re: inline resolve mode
> Hmm....
> First of all, every module must have an ivy.xml file to describe it.
> If what you want to resolve is a module, then you can do that with the
> inline ant tasks. Then you are specifying the module name and letting ivy
> (using your ivy settings) locate the corresponding ivy.xml file, process
> the
> dependencies, etc.
> If what you want to do is define a new module inline (including one or more
> dependencies) and then resolve it, then you are essentially trying to
> "inline" and ivy.xml file and I don't think ivy currently supports that. I
> don't see why you would need the ability to do this anyway... you can
> always
> just put the module meta-data into a local ivy.xml file and then refer to
> it.
> Not sure what you're trying to do but I typically do this kind of thing for
> software projects. Each project has it's own ivy.xml that defines
> configurations like "compile", "test", etc. When I need to build the
> classpath for the "javac" task, I use an inline call to <ivy:cachepath> or
> whatever to get the JARs associated with the "compile" configuration, etc.
> Hope this helps.
> -Archie
> On Tue, Jun 23, 2009 at 1:06 AM, Shawn Castrianni <
>> wrote:
> > I need a way to resolve dependencies of a module WITHOUT an ivy.xml file.
> >  It looks like inline mode is what I want, however, I am not sure about
> > something.  An ivy.xml file can specify more than 1 dependency, each with
> > its own revision constraint and configuration specification.  It looks
> like
> > the inline resolve ant task only allows 1 dependency to be specified with
> 1
> > configuration and 1 revision constraint.  Therefore, it seems that inline
> > resolve is not a complete replacement for an ivy.xml file.  Am I supposed
> to
> > make multiple separate calls to inline resolve for each dependency I have
> > that would normally be listed in an ivy.xml file?  If so, how does the
> > conflict resolution work since each inline resolve operation would not
> know
> > about the previous inline resolve operation to properly resolve
> conflicts??
> --
> Archie L. Cobbs
> ----------------------------------------------------------------------
> This e-mail, including any attached files, may contain confidential and
> privileged information for the sole use of the intended recipient.  Any
> review, use, distribution, or disclosure by others is strictly prohibited.
>  If you are not the intended recipient (or authorized to receive information
> for the intended recipient), please contact the sender by reply e-mail and
> delete all copies of this message.

Archie L. Cobbs

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