CDO Source Installation old
(Includes Net4j Source installation)
The following page is superseded by []
The CDO workspace will be configured with a dedicated JDK, connected with a dedicated target platform to be built against and associated with a dedicated API Baseline to be checked for API compliance against.
As a consequence of the usage of a dedicated target platform you're free to choose any version of Eclipse as your IDE, recent versions preferred. We are using latest I-builds of Eclipse and some tools like Mylyn.
Further we are using a common development folder C:\develop on the local file system which is the parent folder of the IDE installation/extensions, the workspaces folder and the downloads folder. It looks like:
With this new version of the setup instructions most of the complicated steps like downloading needed prerequisites, unzipping and copying them are automated by an Ant script (which is described in the bootstrap chapter. There are still the deprecated manual CDO Source Installation instructions available for archive purposes.
The following instructions are based on these assumptions:
- You want to work on the HEAD development stream. You would have to adjust the bootstrap steps to switch to another stream or version.
- You have basic knowledge about JDT and PDE.
- You are working on a plain old Windows box.
- Create the host workspace folder C:\develop\ws\cdo in the file system
- Start your Eclipse IDE with C:\develop\bin\eclipse\eclipse.exe -data C:\develop\ws\cdo
- Switch to the Plug-in Development perspective
- Import your existing preferences (optional)
- Configure a JDK 1.5 of your choice on the Installed JREs preference page
- Set the Compiler compliance level to 1.5 on the Java Compiler preference page
- Choose one of the bootstrap Team PSFs and store it somewhere in your file system (we use C:\develop\ws\cdo\bootstrap.psf):
- Committers: Don't forget to setup a maintenance workspace by switching the develop.setup project to the maintenance branch, currently R2_0_maintenance!
- Import the downloaded bootstrap Team PSF (ignoring potential warnings about "partial repository" bla bla):
- Now your CDO workspace should look like this:
- Consult and potentially adjust urls-baseline.txt and urls-target.txt.
in order to have it working on linux: adjust url-target.txt and url.baseline.txt: replace http://download.eclipse.org/eclipse/downloads/drops/R-3.5-200906111540/eclipse-SDK-3.5-win32.zip by http://download.eclipse.org/eclipse/downloads/drops/R-3.5-200906111540/eclipse-SDK-3.5-linux-gtk.tar.gz OR http://download.eclipse.org/eclipse/downloads/drops/R-3.5-200906111540/eclipse-SDK-3.5-linux-gtk-x86_64.tar.gz
- Start the Setup-Workspace Java launch config (Run | Run Configurations... | Java Applications | Setup-Workspace)
- Watch the Console view while Setup.java is running.
- Behind the scenes all the files necessary for the API baseline and the target platform of the workspace have been downloaded and installed
- In your Eclipse IDE open the Preferences dialog via the Window menu and go to the Target Platforms page
- Enter the new Location of the target platform (C:\develop\ws\cdo\.target\eclipse):
- In your Eclipse IDE open the Preferences dialog via the Window menu and go to the page API Baselines and press the Add Baseline... button
- Enter the Name (Eclipse 3.5) and Location (C:\develop\ws\cdo\.baseline\eclipse\plugins):
- Leave the Preferences dialog by pressing the Ok button
- Right-click the workspace file /develop.setup/psf/pserver/All.psf and select Import Project Set... and go fetch a coffee
- When the checkout process is finished set the Top Level Elements of the Package Explorer view to Working Sets (local pulldown menu)
- Select Configure Working Sets... (local pulldown menu):