ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mitch Gitman" <>
Subject Re: New to Ivy question
Date Fri, 24 Oct 2008 03:33:41 GMT
When it comes to third-party dependencies, I hate to be reinventing the
wheel, or at least reinventing the wheel from scratch. So I would look to do
either of two things:
* Depend on a public repository directly for those dependencies.
* Create an enterprise repository whose third-party dependencies emulate
those of a public repository. You're not depending on the public repository;
you're just using it as a model for your own local repository.

As for the second option, you could do that manually just by using the
public repository's dependency graphs as a template. Or you could do that in
an automated fashion with a repository copy using the ivy:install Ant task.

To the best of my knowledge, the public repository that typically gets
copied to bootstrap a local repository is the Ibiblio Maven repository. The
downside of that repository is you're limiting yourself to the limited way
Maven expresses dependencies. So from the get-go, you're losing one of the
key advantages of Ivy.

One public Ivy repository I find intriguing is Ivy RoundUp:

What I like is that its dependency configurations really take advantage of
the power of Ivy. Why? Because it's actually an Ivy repository and not a
Maven repository, and its ivy.xml files for frameworks like Spring and
Hibernate really take leverage Ivy's expressiveness together with a real
knowledge of those frameworks. What I don't like is that it makes some
presumptions about how you should use it. Namely, you should always depend
on it directly. Even if you don't want to use Ivy RoundUp directly, you
could gain some value using its Spring and Hibernate ivy.xml files as
templates for your own.

On Thu, Oct 23, 2008 at 10:41 AM, rfkrocktk <> wrote:

> I'm new to Ivy, as you've already gathered, and I'm very interested in how
> it
> can help me resolve my project's dependencies. I'm running a Spring +
> Hibernate setup on a J2EE server, and I need to know which libraries I'll
> need to get the whole thing going. I've already got an existing Hibernate
> setup working for this server, but I'm wondering how in the heck Ivy would
> know which libs I need to get Hibernate and Spring working together. Also,
> the latest version of the server has changed how things work, has upgraded
> to Spring 2.25, and has removed some JARs that my existing setup depends
> on.
> I can't nail down specifically which JAR's are necessary, so I'm basically
> screwed until I can figure this out.
> Maybe this isn't even an Ivy question, I don't know. Is there a way to find
> out what libraries I'll need for any project?
> --
> View this message in context:
> Sent from the ivy-user mailing list archive at

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