Jump to: navigation, search

WTP/Build/WTP Developer Installation Quick Guide

< WTP‎ | Build
Revision as of 15:05, 17 January 2007 by Jlanuti.us.ibm.com (Talk | contribs)

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:


# Build Stream are one of R0.7, R1.0, R1.5, R2.0

# Build area is one downloads or 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

# This is the home dir for build tasks
#   i.e. downloads folder etc.

# This is where the deriver will be installed
#   i.e. downloads folder etc.

# This is the folder under build.home where the
# scripts will look for previosly doenloaded files
#   i.e. downloads folder etc.


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:

<?xml version="1.0"?>
<!-- ====================================================================== 
    Properties that must be passed to this script can be found in 
     ====================================================================== -->
<project name="wtp-installer" default="get">

	<property file="build.properties" />
	<property file="./tmp/releng/maps/dependencies.properties" />
	<property name="dependencyTargets" value="./tmp/releng.wtpbuilder/scripts/dependency/build.xml" />
	<property name="local.cache.dir" value="${build.home}/${build.local.repository}" />
	<property name="base.install.dir" value="${targetDir}/${wtp.buildLabel}" />

	<!-- We form these properties dynamically to download the latest build -->
	<property name="wtp.url" value="http://download.eclipse.org/webtools/${wtp.buildArea}/drops/${wtp.buildStream}/${wtp.buildLabel}" />
	<property name="wtp.releng.url" value="http://download.eclipse.org/webtools/downloads/drivers" />
	<property name="wtp.file" value="wtp-sdk-${wtp.buildLabel}.zip" />
	<property name="wtp.name" value="WTP sdk ${wtp.buildLabel}" />
	<property name="wtp.description" value="WTP sdk ${wtp.buildLabel}" />

	<target name="get" depends="releng">
		<delete dir="${base.install.dir}" failonerror="false" />
		<mkdir dir="./tmp" />
		<antcall target="releng" />
		<antcall target="getAndInstall">
			<param name="groupId" value="emf" />
		<antcall target="getAndInstall">
			<param name="groupId" value="gef" />
		<antcall target="getAndInstall">
			<param name="groupId" value="jem" />
		<antcall target="getAndInstall">
			<param name="groupId" value="eclipse" />
		<antcall target="getAndInstall">
			<param name="groupId" value="wtp" />


	<target name="getAndInstall">
		<ant antfile="${dependencyTargets}" target="checkDependency">
			<property name="groupId" value="${groupId}" />
		<ant antfile="${dependencyTargets}" target="installDependency">
			<property name="groupId" value="${groupId}" />
			<property name="install.destination" value="${base.install.dir}" />

	<target name="releng">

		<available file="./tmp/releng/maps/dependencies.properties" property="map.exists" />
		<available file="./tmp/releng.wtpbuilder/scripts/dependency/build.xml" property="releng.exists" />
		<antcall target="checkout-maps" />
		<antcall target="getwtpbuilder" />

	<target name="checkout-maps" unless="map.exists">

		<cvs quiet="true" cvsRoot=":pserver:anonymous@dev.eclipse.org:/cvsroot/webtools" package="releng/maps/build.cfg" dest="./tmp" tag="${wtp.cvsTag}" />
		<cvs quiet="true" cvsRoot=":pserver:anonymous@dev.eclipse.org:/cvsroot/webtools" package="releng/maps/dependencies.properties" dest="./tmp" tag="${wtp.cvsTag}" />


	<target name="getwtpbuilder" unless="releng.exists">
		<property file="./tmp/releng/maps/build.cfg" />
		<delete dir="./tmp/releng.wtpbuilder" failonerror="false" />
		<echo message="Version tag for releng.wtpbuilder is: ${wtpBuilderVersion}" />
		<cvs quiet="true" cvsRoot=":pserver:anonymous@dev.eclipse.org:/cvsroot/webtools" package="releng.wtpbuilder/scripts/dependency" dest="./tmp" tag="${wtpBuilderVersion}" />




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:


So you can adjust the "cvsRoot" attribute of the cvs tags accordingly.

The other thing you may need to do is add a setproxy task to the get recipe. Let's say that your proxy is called "proxy" and its port is 82, then you could add:

<setproxy proxyhost="proxy" proxyport="82"/>

to the "get" target above. See http://ant.apache.org/manual/OptionalTasks/setproxy.html for setproxy options.

Back to WTP Build Process and Procedures
Back to Web Tools Wiki Home