Daniel Kulp wrote:
On Fri June 26 2009 6:50:49 am Robert Godfrey wrote:
I've not used Ivy, so I may be underestimating its cleverness; but I'm
not sure how we can get away without the meta data being in effect a
manually maintained duplicate of data that is mastered elsewhere.  In
particular we want/require to build of versions of jars that are in
our repo (so that we can have repeatable builds).

Just want to inject in here. It has NOTHING to do with repeatable builds. The Jars in central NEVER change and are NEVER deleted. If you depend on jars at central, the builds would be repeatable just fine.

Actually our issue WAS with repeatable builds. We pretty much had every issue this guy talks about and more:

http://ignorancecompounded.blogspot.com/2008/10/maven-sucks.html

The problem you had with maven were:
1) You didn't want to use released jars at central. You wanted your own versions of various things from who knows where. You didn't want to use officially released jars.

We did use a patched version of MINA, but I believe we were forced to abandon it due to problems with maven. I'm not sure which version we use now, but if it is patched or if we need to patch it again, then that would be a problem for any poms we produce.

2) The maven plugin version issues (which did make builds non-reproducable, but that is fixed in maven >= 2.0.8 and was easily worked around by specifying plugin versions)

This isn't so trivially worked around. Even if you nail down all the versions of every dependency in your own pom, you transitively depend on other people's poms, and their dependencies may use snapshots or version ranges. This means that in general it's very difficult to ensure that you're working with the same set of dependencies as another developer or as yourself 5 minutes from now when maven decides to download a different set for you.

--Rafael

---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:[email protected]

Reply via email to