Embedding Ivy to manage repositories.

[Samuel Cox <cr...@gmail.com>]

Hi,

I'm working on software that will need to run on the nodes of a network. 
  A node's software will need to access various repositories containing 
build artifacts.  An artifact might have a dependency on another 
artifact.  The nodes will need things like list the available artifacts 
in the repo, list dependencies, etc.

I have looked at embedding Maven, but it is rather large.  Ivy is the 
next up.  Do you think I would be able to achieve something like this by 
embedding Ivy?  How stable is the API?  Would I need to do things via 
ant tasks?

Any tips or thoughts are appreciated.

--
Samuel Cox

Re: Embedding Ivy to manage repositories.

[Archie Cobbs <ar...@gmail.com>]

My $0.02...

I would start by using the ant API to ivy first. Last time I checked, the
ivy code was somewhat murky and very poorly documented (javadoc is almost
nonexistent).

You can have your code spit out temporary build.xml files, then invoke ant
programatically (which is easy), and then grab whatever files were produced
by the ant task.

Then later, as an optimization, you could figure out how to convert the ant
tasks into direct API calls.

-Archie

On Mon, Jan 26, 2009 at 2:45 PM, Samuel Cox <cr...@gmail.com> wrote:

> Hi,
>
> I'm working on software that will need to run on the nodes of a network.  A
> node's software will need to access various repositories containing build
> artifacts.  An artifact might have a dependency on another artifact.  The
> nodes will need things like list the available artifacts in the repo, list
> dependencies, etc.
>
> I have looked at embedding Maven, but it is rather large.  Ivy is the next
> up.  Do you think I would be able to achieve something like this by
> embedding Ivy?  How stable is the API?  Would I need to do things via ant
> tasks?
>
> Any tips or thoughts are appreciated.
>
> --
> Samuel Cox
>



-- 
Archie L. Cobbs