ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Shawn Castrianni <Shawn.Castria...@halliburton.com>
Subject RE: inline resolve mode
Date Tue, 23 Jun 2009 17:15:18 GMT
The addition of these extraDependencies is done at runtime and the ivy.xml file is never modified.

The ANT code would do something like:

1. run normal resolve using ivy.xml file
2. loop through extraDependencies property, and for each extra dependency run inline resolve

The problem with this is what my original email stated, that I am guessing that the multiple
calls to resolve (one normal and the rest inline) will not be able to perform conflict management
since the resolve operations are separate.

---
Shawn Castrianni


-----Original Message-----
From: Niklas Matthies [mailto:ml_ivy-user@nmhq.net] 
Sent: Tuesday, June 23, 2009 11:39 AM
To: ivy-user@ant.apache.org
Subject: Re: inline resolve mode

On Tue 2009-06-23 at 11:18h, Shawn Castrianni wrote on ivy-user:
> 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

I don't understand how adding dependencies to the Ivy file using Ant
instead of manually will prevent the modified Ivy file to be committed.

-- Niklas Matthies

----------------------------------------------------------------------
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.

Mime
View raw message