Updating the JDK for zero builds

This is a step-by-step list of instructions for updating the JDK that gets packaged in the installer and used in the tests on the build servers.

1. Download the JDKs: Thus far the JDKs have come directly from the Hursley build system called espresso or from JIM. Note: You'll need a CMVC account to access espresso.
2. Create a location on the build machine (aeneid) for the new JDKs that reflects their version (the JDKs from JIM do not include the version in the filename so you will have to expand them and run 'java -version' to get the info), e.g. /builds/prereqs/jdks/3260ifx-20080507_01. Then, copy the downloaded JDKs into this directory. This will be the location used by the build scripts to package the JDK in the installers.
3. Edit and commit the build file to pick up the new JDKs. Edit the following lines in /trunk/INSTALL/zero.install.build/build.xml:

   • <property name="win.vm"  value="<path to new win zip"/>

   • <property name="lin.vm"  value="<path to new linux archive"/>

   • <property name="jdksource" value="espresso"/> 
             or <property name="jdksource" value="JIM"/>

     (depending on the source)
4. Replace the current linux (aeneid) test JDK with the new one. It is located at /opt/ibm/java2-i386-61. I usually move the current to a backup location then create a new java2-i386-61 directory to extract the JDK. Note the current directory structure - there is no top-level dir under java2-i386-61.
5. Replace the current windows (9.42.118.131) test JDK with the new one. It is located at c:/build/java.
6. Update symlinks on aeneid at /usr/local/apache2/htdocs/sr1/linux and /usr/local/apache2/htdocs/sr1/windows to point to the new jdks in /builds/prereqs/jdks/... Note: These are just so developers can download for their own testing

-- ajtarter - 08 May 2008