Skip to Content
Last modified by Pascal Robert on 2012/07/21 20:39
From version 41.1
edited by Kieran Kelleher
on 2007/12/10 21:15
Change comment: There is no comment for this version
To version 45.1
edited by Kieran Kelleher
on 2007/12/10 20:48
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -20,26 +20,10 @@
20 20  
21 21  * So, download the script and drag it to the root of your project.
22 22  
23 -* Open the Ant run configuration for the script by right-clicking on the script and selecting the menu shown below.
23 +* Next, right-click on the script and select the "clean" and compileAndBuild" tasks. If necessary use the "Order..." button to ensure that "clean" comes before "compileAndBuild".
24 24  
25 25  {{info title="Using the Ant Script"}}
26 - !running_the_script.jpg!
27 27  
28 -{{/info}}
27 +!running_the_script.jpg!
29 29  
30 -* Next select the "clean" and compileAndBuild" tasks. If necessary use the "Order..." button to ensure that "clean" comes before "compileAndBuild".
31 -
32 -{{info title="Configure the Ant Tasks to be run"}}
33 - !ant_tasks.jpg!
34 -
35 35  {{/info}}
36 -
37 -* Click the Run button to run the ant script and your fully embedded split install deployment bundles will be created in the "dist" folder.
38 -
39 -=== Customization ===
40 -
41 -It is common to want to use custom bundle build names. There are a number of advantages to having a unique application name for each build:
42 -
43 -* For example, you might want to have a name that reflects the current revision so that a clean bundle is deployed without overwriting older version bundles on the servers.
44 -* If the current and new versions of the app are compatible with the current database schema, smooth zero-downtime "rolling upgrades" are possible by using this strategy... and the ability to switch back to the older version if an unexpected deployment problem occurs
45 -* Because we are using fully embedded split bundles, the unique deployment name will ensure that web server resources all get a new URL ensuring that older versions cached by browsers will not be used for new deployed version apps ... which can be important for javascript and image updates for example.