Steve,

I blew away my entire build last night (specifically, deleted the install & deploy directories in keel-build), ran a completeinstall (which tied up my phone line for 2.5 hrs), and this thing still came back.

Ouch....I am sending this hoping to avoid that kind of wasted time for you in the future.


You can always delete install, without incurring a time penalty, in-fact assemble-deploy pretty much does that unless you specify "dont.delete.install" property.

The entire deploy directory should not be wiped out (at least, there shouldn't be a need, you can if you want to). If you really suspect something, then I'd go as far as deleting deploy/jakarta-tomcat-4.1.27.

If you really want to delete deploy, then try this. Save off all the *.zip/*.gz etc distributions from deploy somewhere else, delete deploy, and put just the saved ones back. This will save you the download time.

ant completeinstall is the equivalent of the following, which you can run individually:

ant download-keeltools (which you can skip if you save and restore the dist(s))
ant install-keeltools
ant assemble-deploy


Shash

http://keelframework.org/documentation
Keelgroup mailing list
[EMAIL PROTECTED]
http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com

Reply via email to