replacing a build dependency system with gump

[Leo Simons]

Hi gang,

I've been experimenting with removing the Avalon-Excalibur ant-based dependency mechanism, and instead relying on gump to track the dependencies. This turns out to be pretty easy to do, but it leads to a dilemma: while I want my nightly builds to be done using the-latest-of-everything, I want my releases to be done using the-latest-release-of-everything.

This is also easily solved. You need 2 project/profile definition sets, where the new set is definitions where the-latest-release-of-everything is defined just like all the other binary packages. Downloading and installing the latest-release-of-everything prior to building can be rather painful in the java world (it's not like there's .deb files for each project), which is of course why the maven peeps are setting up http://www.ibiblio.org/maven/.

I'm wondering where to go next. Would it be a good idea to copy some of maven's auto-get-this-jar-from-repo functionality to gump, or should gump remain purely focused on integration builds?

thoughts?

cheers,

- Leo



--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>