Aidan Skinner wrote:
On Mon, Jun 29, 2009 at 8:36 PM, Bryan Kearney<[email protected]> 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.
We can.. as long as we bring in the pom/ivy artifacts as well. It would
be easy to make it a flat file if we have
org.apache.mina-mina.core-1.0.1.jar
org.apache.mina-mina.core-1.0.1.pom
If folks can live with that, it can be flat. We need the upstream pom or
ivy.xml checked in.
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. :)
Thanks. If other folks are ok.. I will complete out the patch, but I
want to get comments on what is good/bad before I do more.
-- bk
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
