Re: Quick(er) deployment

Justin,

There was a "overwrite=true" forcing the copy of the base webapp 
(webapp-minimal) on every build.  I have taken it out, but just in case 
we need to put the overwrite back in, I have made that into a property 
that is settable in ant.properties (default is false, for no overwrite).

Here's the Wiki page: 
http://66.105.113.115/vqwiki-2.3.5/jsp/Wiki?SpeedyBuild

Wait a day for anon. CVS to sync up at SF, then update the 
keel-build/import directory files and keel-build/ant.properties.

HTH,
Shash

PS: It still pauses a bit on copying webapp-minimal over, that is 
because Ant is doing timestamp based dependency analysis to figure out 
if anything needs to get copied over...but overall it should be much faster.

Michael Nash JGlobal.com wrote:

>Justin:
>
>  
>
>>Having read the thread below and the binary dist article on the Wiki, I still can't seem to get a faster deployment working. When deploying Cocoon as the client, the keel_bundle_client:basewebappdir task takes upwards of 2 minutes to copy over 5000+ Cocoon files. I can't tell if the changes to the dont.delete.delploy, dont.delete.install, and assemble.webapp.dir properties did anything. Isn't there a way to deploy Keel without having to deploy Cocoon (Struts, etc.)? Any help would be much appreciated.
>>    
>>
>
>There's a number of ways to optimize the deploy, depending on what you want to do - the default just uses what is essentially the simplest, but slowest way.
>
>At a high level, here are some of the options:
>
>1. Don't deploy all the way to a webapp every time, but deploy changed files into a directory, then point Tomcat at this directory (or have the directory be in the webapps dir of Tomcat).
>2. Deploy Keel's client & server seperately. There are ant targets "assemble-deploy-client" and "assemble-deploy-server" to assist this. You would then need to specify a communications layer between the two (e.g. JMS, Sockets, Axis).
>
>5000+ Cocoon files sounds very high - I'll have to run mine here & see what it's copying, it shouldn't be that bad. I know I'm not taking 2 minutes on a build/deploy cycle!
>
>Also, combinations of the above methods can be done - e.g. even if you're doing a "single-VM" (in other words, a single webapp) deploy of Keel, you can still deploy just the client or just the server portions.
>
>This sounds like a fine topic for a HOWTO, given that there are a lot of different ways to tackle it, and there are no doubt places where the build scripts can be improved to make some of the options easier to use.
>
>Mike
>
>  
>
>>- Justin
>>
>>--
>>ThatOne Company
>>http://www.thatone.com/
>>
>>-----Original Message-----
>>From: user-keelframework.org-admin-rI8AND0JKYOgdSakss0wQjfEH8FBEnyy@public.gmane.org [mailto:[email protected]] On Behalf Of Shash Chatterjee
>>Sent: Tuesday, April 06, 2004 6:59 AM
>>To: user-6VIttnCrOeJXNEnpj1eHPNi2O/[email protected]
>>Subject: Re: [Keel User] Quick(er) deployment
>>
>>Justin,
>>
>>    
>>
>>>I'm just getting off the ground with Keel, building my first app. Is 
>>>there a faster way to deploy an app (single VM, Tomcat, Struts)  
>>>without having to stop Tomcat and run the entire assemble-deploy?
>>>
>>>      
>>>
>>Look at this thread:
>>http://lists.keelframework.com/pipermail/keelgroup-keelframework.com/2004-January/003204.html
>> 
>>
>>In short, setup Tomcat for context reloading, change Keel properties to not build a WAR, but assemble webapp in a dir, and provide the dir path.  Also, need to set properties to not delete the install/deploy dirs.
>>
>>HTH,
>>Shash
>>
>>PS: The Keel developer archives are not searchable currently, but you can go to http://gmane.org/ and search on the gmane.comp.java.keel.devel and gmane.comp.java.keel.user groups. 
>>_______________________________________________
>>User mailing list
>>[email protected]
>>http://lists.keelframework.org/listinfo.cgi/user-keelframework.org
>>
>>
>>_______________________________________________
>>User mailing list
>>[email protected]
>>http://lists.keelframework.org/listinfo.cgi/user-keelframework.org
>>    
>>
>
>
>  
>