Minor change to support a solution to a deployment issue I hit once in a while: When doing a "hot-deploy" of a webapp to some servers (notably JBoss), the server will sometimes start to "un-jar" the war file before it's finished copying, resulting in a failed deployment. If you add a deploy.webapp.tmp property, the "deploy" process will copy the .war to that directory first, then "move" it to the final destination (which is just a rename, not a copy). This helps if you're deploying over an NFS share or something where the copy is slow. If you don't set the property, nothing is affected, it just deploys as before.
Michael Nash JGlobal Ltd. http://www.jglobal.com Bahamas Commerce and Trade http://www.bahamascommerce.com http://keelframework.org/documentation Keelgroup mailing list [EMAIL PROTECTED] http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com
