A Quick Guide to Installing a WTP Build for Testing or as Development Target

WTP developers install WTP builds that are available at committers or downloads areas frequently for testing or using these as plugin development targets. Since each build has its own set of prerequisites, the installation process involves downloading WTP and its prereqs such as emf, gef, jem and eclipse sdk. To simplify this process I have created a scripts that uses the install scripst from the actual releng builder that was used to create a particular build. To use it create simple eclipse project or just copy these scripts into a folder and run "ant -f install.xml get". The script should do all the work for you.

To use these scripts you should have apache ant (v1.6 or better), a JDK (v1.4.2 ro higher), and CVS installed on your machine. They should be on your path.

First file you should create is the build.properties. You modify this file to change the build you want to install or where you want files to be installed etc. You should review these properties before each install:

baseos=win32
basews=win32
basearch=x86
#-------------------------------------------------
# Build Stream are one of R0.7, R1.0, R1.5, R2.0
#-------------------------------------------------
wtp.buildStream=R1.5
#-------------------------------------------------
# Build area is one downloads or committers
#-------------------------------------------------
wtp.buildArea=committers
#-------------------------------------------------
# label of the Build to install
# e.g. M-1.5.1-200607141912
#
# cvstag is a derived label that you must provide
# in order to automtaically access the correct
# maps and wtp builder
# it is "v"+"buildType"+"buildTimeStamp"
# e.g. vM200607141912
#-------------------------------------------------
wtp.buildLabel=M-1.5.1-200607141912
wtp.cvsTag=vM200607141912
#-------------------------------------------------
# This is the home dir for build tasks
# i.e. downloads folder etc.
#-------------------------------------------------
build.home=C\:/dev/build-home
#-------------------------------------------------
# This is where the deriver will be installed
# i.e. downloads folder etc.
#-------------------------------------------------
targetDir=${build.home}/drivers
#-------------------------------------------------
# This is the folder under build.home where the
# scripts will look for previosly doenloaded files
# i.e. downloads folder etc.
#-------------------------------------------------
build.local.repository=downloads

Second file you should create is the ant script for installation, install.xml. You do not need to modify anything in this this file, just change the properties we described before:

If you are behind a proxy you may need to make a few changes to the install.xml script above. First, you will need to add your proxy settings to each of the cvs tasks. The proxy information is of the form: