qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Aidan Skinner <aidan.skin...@gmail.com>
Subject Re: RFC: Ivy Integration (Was RFC: Maven and the Java Build)
Date Wed, 01 Jul 2009 10:02:49 GMT
On Mon, Jun 29, 2009 at 8:36 PM, Bryan Kearney<bkearney@redhat.com> wrote:

> Taking what Aiden suggested. Here is a first cut at ivy integration. What
> this does is:
> 1) Require that every module have an ivy.xml file which is contains all the
> dependencies.
> 2) Defines a depVersions.properties file at the root project to control the
> actual version numbers.
> 3) Builds a pom file (DRY) with every build (see build/pom).

I really like this approach.

> A) Use the local lib file. If the requirement is to check in every version,
> we could do that by refactoring the lib directory to be a mini ivy or maven
> repo.

I'd rather write a resolver which looks in a flat directory. I know
it's a bit more work, but will make it much, much easier to get our
stuff downstream.

> Can folks please take a look at this patch and let me know what it misses
> from your requirements. To install it, please do the following:

I gotta say, that's pretty slick. :)

- Aidan
Apache Qpid - AMQP, JMS, other messaging love http://qpid.apache.org
"A witty saying proves nothing" - Voltaire

Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org

View raw message