Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "CDO Source Installation (CVS, deprecated)"

(Introduction)
(Introduction)
Line 12: Line 12:
 
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 [http://www.eclipse.org/mylyn Mylyn].
 
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 [http://www.eclipse.org/mylyn Mylyn].
  
We are using a common development folder <tt>C:\develop</tt> 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:<br>[[Image:DevelopFolder.png]]
+
Further we are using a common development folder <tt>C:\develop</tt> 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:<br>[[Image:DevelopFolder.png]]
  
 
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|bootstrap chapter]]. There are still the [[CDO Source Installation (deprecated)|deprecated manual CDO Source Installation]] instructions available for archive purposes.
 
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|bootstrap chapter]]. There are still the [[CDO Source Installation (deprecated)|deprecated manual CDO Source Installation]] instructions available for archive purposes.

Revision as of 14:49, 28 June 2008

(Includes Net4j Source installation)


Introduction

This page explains how to install an Eclipse workspace that is ready to be used to develop and build CDO and Net4j (subsequently subsumed as CDO workspace).

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:
DevelopFolder.png

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.


Bootstrap

  • 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
  • Download the bootstrap Team PSF and store it somewhere in your file system (we use C:\develop\ws\cdo)
  • Import the downloaded bootstrap Team PSF (ignoring potential warnings about "partial repository" bla bla):
    Bootstrap1.png

  • Now your CDO workspace should look like this:
    Bootstrap2.png

  • Consult and potentially adjust setup-workspace.properties:
    Bootstrap3.png

  • Start the Setup Workspace Ant launch config (Run | External Tools | External Tools Configurations...)
  • Watch the Console view while Ant is running (here is an example output)
  • Behind the scenes all the files necessary for the API baseline and the target platform of the workspace have been downloaded and installed


Target Platform

  • 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\metadata\.target):
    TargetPlatformPrefs2.png

  • Press the Reload button (just to be sure)
  • Finally verify the Plug-ins list and press the Ok button


API Baseline

  • 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 (CDO Baseline 1.0.0) and Location (C:\develop\ws\cdo\.metadata\.baseline):
    NewBaseline2.png

  • Verify the Plug-ins/bundles list and press the Finish button to return to the Preferences dialog:
    BaselinePrefs2.png

  • Leave the Preferences dialog by pressing the Ok button


Source Checkout

  • 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):
    WorkingSets.png

  • You're finished! Now you should have a complete CDO workspace:
    CheckoutResult.png



Wikis: CDO | Net4j | EMF | Eclipse

Back to the top