Jump to: navigation, search

Difference between revisions of "Developer's guide to upgrading the AJDT build to a newer version of Eclipse"

(Updating the upgrading instructions)
 
(7 intermediate revisions by the same user not shown)
Line 1: Line 1:
Steps required to change the version of Eclipse used to build and AJDT and run the tests.
 
As an example we will consider an upgrade from Eclipse 3.3M3 to 3.3M4:
 
  
Download new Eclipse-SDK (such eclipse-SDK-3.3M4-linux-gtk.tar.gz) and also eclipse-test-framework-3.3M4.zip (listed under  JUnit Plugin Tests and Automated Testing Framework)
+
* See [Developer's guide to driving the AJDT build process] and get the build process working locally first on the current version of Eclipse.
 
+
* Edit the local.properties file to select the appropriate workspace and build destination.
From the CruiseControl build directory on the build machine, rename old dir "eclipse33" to "eclipse33-old-M3". Create new dir "eclipse33" and unpack new SDK into it - so that you have a path of eclipse33/eclipse/startup.jar.
+
* Edit provisioning_support/download.properties to add the new version of Eclipse that you will be using
 
+
* Edit buildAll.xml and replace references to ${build.url.3.X} to your new version of Eclipse.  Note that only the target eclipse must be changed. The build Eclipse can remain in the old version.
Go to "test" sub-dir and rename old dir "eclipse33" to "eclipse33-old-M3". Unpack new SDK again - so that this time you have a path of eclipse33/startup.jar. Also unpack the test framework zip file at the same level. Go into eclipse33/plugins and rename org.eclipse.test_?.?.? to just "org.eclipse.test".
+
* Optionally update the bundles in the build_bundles folder.
 
+
The script which runs the tests expects a startup.jar file in the "eclipse33" directory. Newer eclipse builds don't have this, so it needs to be copied from the plugins dir with "cp plugins/org.eclipse.equinox.launcher_.*.jar startup.jar"
+
 
+
----
+
 
+
That should be it, but there are often some workarounds required for specific issues. Here is the current list:
+
 
+
Delete test/eclipse33/plugins/org.eclipse.jdt.compiler.tool.*.jar as this new plugin requires Java 6, so will cause a warning which will result in a test failure (the tests are run under Java 5)
+
 
+
Edit test/eclipse33/plugins/org.eclipse.test/library.xml and add "-XX:MaxPermSize=128m" to the value of the "extraVMargs" property (see bug 130545)
+
 
+
----
+
 
+
*Update:*
+
 
+
Here is how I upgraded from Eclipse 3.4 RC1 to Eclipse 3.4 finalSlightly different than above:
+
 
+
# Download eclipse classic: eclipse-SDK-3.4-linux-gtk.tar.gz
+
 
+
# Move eclipse34 directory to eclipse34rc1-old
+
 
+
# Unpack downloaded zip into eclipse34/eclipse directory
+
 
+
# Move test/eclipse34 directory to test/eclipse34rc1-old
+
 
+
# Unpack again into test directory
+
 
+
# Copy test/eclipse34rc1-old/*test*.xml and test/eclipse34rc1-old/ui_session_sniff_folder/ into test/eclipse34
+
 
+
# Copy the test framework plugins (ie- eclipse34rc1-old/plugins/*test*) into the plugin directory of eclipse34 for both places I unpacked (note that for 3.5 or later versions, you will need to download the eclipse testing framework separately and follow the steps above)
+
 
+
# Run ant -f build-ajdt1.6.xml to make sure that the new eclipse version works
+
  
 
[[Category:AJDT]]
 
[[Category:AJDT]]

Latest revision as of 09:22, 17 March 2010

  • See [Developer's guide to driving the AJDT build process] and get the build process working locally first on the current version of Eclipse.
  • Edit the local.properties file to select the appropriate workspace and build destination.
  • Edit provisioning_support/download.properties to add the new version of Eclipse that you will be using
  • Edit buildAll.xml and replace references to ${build.url.3.X} to your new version of Eclipse. Note that only the target eclipse must be changed. The build Eclipse can remain in the old version.
  • Optionally update the bundles in the build_bundles folder.