Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ivy-user@ant.apache.org
Received-SPF: pass (nike.apache.org: local policy)
Date: Fri, 30 Apr 2010 17:31:32 +0200
From: Niklas Matthies <ml_ivy-user@nmhq.net>
To: ivy-user@ant.apache.org
Subject: Re: example ivy & build.xml file for spring/jsf/hibernate project
Message-ID: <20100430153132.GB16294@nmhq.net>
Mail-Followup-To: ivy-user@ant.apache.org
References: <22461453.post@talk.nabble.com> <22463169.post@talk.nabble.com>
 <22464286.post@talk.nabble.com> <22465286.post@talk.nabble.com>
 <28405448.post@talk.nabble.com>
 <r2j3bc8237c1004291359yb29c4d09sd2dc1d519c102287@mail.gmail.com>
 <28413244.post@talk.nabble.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <28413244.post@talk.nabble.com>
User-Agent: Mutt/1.5.18 (2008-05-17)

On Fri 2010-04-30 at 08:00h, infinity2heaven wrote on ivy-user:
:
> Is what I'm asking that hard?

I would maybe put it this way: Ivy is a tool for library providers to
make things simpler for their library users. But for the library
providers themselves, doing this in a good way is not necessarily very
simple, depending on the complexity of the library. The problem you
have is that the providers of the libraries you're interested in
either don't use Ivy at all, so you have to do their work, or they use
Ivy in different ways (different conf setup etc.), so you have to do
some integration work to match it up with the conventions used by
other libraries, and with your own.

The flexibility that makes Ivy powerful means at the same time that
there are no fixed predetermined conventions, so everyone uses
slightly different (or sometime very different) setups.

And then Ivy only does the dependency management part, so the task of
writing build scripts that meet your needs remains yours.

But to answer your question: Yes, it's that hard, unfortunately.

-- Niklas Matthies