* 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.

−

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.

+

[[Category:AJDT]]

−

+

−

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".

+

−

+

−

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)

+

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.