You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ivy-user@ant.apache.org by Mike Goodwin <mi...@cantab.net> on 2010/05/04 01:55:48 UTC
Ivy with multi modules
Hello,
I have a couple of questions regarding ivy in a multi-module environment.
Is it possible in ivy to optionally 'resolve' a dependency directly to
a classes directory instead of a jar? This would be a useful thing to
be able to do during development. As I understand IvyDE does do
something similar, but I would like to be able to achieve this only in
Ivy.
The second thing is, is it possible to create a resolver which will
checkout and build a dependency from source control? Is it possible to
configure such a resolver inside the dependee project/ivy.xml so that
it can be versioned with the dependee code?
thanks!
mike
Re: Ivy with multi modules
Posted by Archie Cobbs <ar...@gmail.com>.
On Mon, May 3, 2010 at 6:55 PM, Mike Goodwin <mi...@cantab.net>wrote:
> The second thing is, is it possible to create a resolver which will
> checkout and build a dependency from source control? Is it possible to
> configure such a resolver inside the dependee project/ivy.xml so that
> it can be versioned with the dependee code?
>
Yes, you can do this with the packager resolver. You will need to set
restricted="false" to enable support for arbitrary ant tasks (including
source control checkout, ant, etc.), and assemble a repository containing
the ivy.xml and packager.xml files that describe the modules and how to
checkout and build them. If you are doing this with internal projects, then
each project could revision and publish its own instructions, etc.
To version your settings, just check ivysettings.xml into your source
control repository along with the rest of your source code.
-Archie
--
Archie L. Cobbs