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
]
Sent: Tuesday, June 23, 2009 9:41 AM
To: ivy-user@ant.apache.org
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
Tharp
Sent: Tuesday, June 23, 2009 11:26 AM
To: ivy-user@ant.apache.org
Subject: Re: inline resolve mode
Why not allow your users to create a second ivy.xml file and then have the
switch point to that second ivy file? That way they can utilize the full
feature set of Ivy and if they accidentally
[mailto:ml_ivy-u...@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
