Sam Ruby wrote:
The idea I was toying with wasLeo Simons wrote:
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?
Being able to get a jar would be very helpful for retrieving the redistributable components of http://cvs.apache.org/builds/gump/latest/packages.html. My only concern is that I don't want the people who are creating a project to be able to dictate the versions of the dependencies used. They should get the first say, of course, but the person doing the integration should get the final say.
changing the "drop project becuse missing dependency foo" step of
gump to be "adding project foo, to the list of downloads" and then
have ruper grab all the files and place them in the "packages dir".
see http://krysalis.org/cgi-bin/krywiki.pl?RuperDependTask
<ruperDepend> has gump <depend> tasks as nested elements, the only addition is a "repository" element so ruper knows where to look for the jar at and a optional "version" attribute..
Ruper is pretty good at handling different versions.
The ruperDepend code is working and tested
see http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/krysalis/krysalis-ant-tasks/src/test/org/krysalis/ant/taskdefs/RuperDependTaskTest.java?rev=HEAD&content-type=text/vnd.viewcvs-markup .
Although it still fails in centipede because the Ant Reference to the generated path, is not available outside of the getcorelibs import.
--
Nick Chalko Show me the code.
Centipede
Ant + autodownloadable build plugins + needed jars autodownload.
http://krysalis.org/centipede
---------------------------------------------------------------------
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
