Difference between revisions of "CDO Source Installation"

From Eclipsepedia

Jump to: navigation, search
Line 20: Line 20:
 
* '''Buckminster - Git Support'''
 
* '''Buckminster - Git Support'''
 
* '''Buckminster - PDE Support'''
 
* '''Buckminster - PDE Support'''
 +
 +
'''Committers''': Please do not forget to install our versioning tool from [http://download.eclipse.org/modeling/emf/cdo/updates/integration http://download.eclipse.org/modeling/emf/cdo/updates/integration]:
 +
 +
[[Image:CDO_Versioning_Tool.png]]
  
 
Now you have prepared your IDE with the required tools.
 
Now you have prepared your IDE with the required tools.
Line 66: Line 70:
  
 
Note, that re-importing doesn't update your source from the Git repository. Use EGit for this purpose!
 
Note, that re-importing doesn't update your source from the Git repository. Use EGit for this purpose!
 
== Tooling (Developers only) ==
 
 
Please do not forget to install install our versioning tool from [http://download.eclipse.org/modeling/emf/cdo/updates/integration http://download.eclipse.org/modeling/emf/cdo/updates/integration].
 
 
[[Image:CDO_Versioning_Tool.png]]
 

Revision as of 07:16, 4 January 2012

Contents

Introduction

This tutorial describes how to install the CDO workspace using Buckminster.
The sources can also be browsed through the Git web interface.

Prepare the IDE

Download and install Eclipse 3.7 or 3.8 from [1]

Then open a fresh development workspace.

Cdo source1.png


Select the Indigo (for 3.7) or Juno (for 3.8) p2 repository and install the following features:

  • EMF - Eclipse Modeling Framework SDK
  • Graphical Modeling Framework SDK (needed for CDO Dawn)
  • Eclipse EGit (Team Provider)

Select the Buckminster p2 repository and install the following features:

  • Buckminster - Core
  • Buckminster - Git Support
  • Buckminster - PDE Support

Committers: Please do not forget to install our versioning tool from http://download.eclipse.org/modeling/emf/cdo/updates/integration:

CDO Versioning Tool.png

Now you have prepared your IDE with the required tools.

Create the API Baseline

Now an API baseline will be created. Non-committers may skip this section.

  • Create a new workspace project called "_baseline"

Cdo export targetdef0.png

  • Download the 4.0 baseline from SourceForge and extract it into the _baseline project.
  • Now add the API baseline: Open the Preferences (Window->Preferences) and open the "API Baselines" page.

Cdo export targetdef3.png

  • Click "Add Baseline...". Give it the name CDO 4.0 Baseline and choose the path to your _baseline project as destination. Then the API baseline is created and set active for your workspace.

Cdo export targetdef4.png

Materialize the Sources and the Target Platform

The materialization of the workspace contents (sources and binaries) will be performed by Buckminster with the cooperation of EGit and p2. For EGit to work properly please create the folder ${user.home}/git on your hard disk.

Then start the Buckminster import wizard:

Cdo import1.png

Point it to the Buckminster MSpec of CDO: [2]

Cdo import2.png

Press the Load button and wait until Buckminster has resolved all the dependencies. Go and fetch a coffee, or two, or three...

Cdo import3.png

Finally hit the 'Finish' button

Cdo import4.png

Updating the Workspace

You can update your development workspace by re-importing the local.mpec (right-click + Buckminster + Import...). Then the whole workspace and the target platform are updated.

Note, that re-importing doesn't update your source from the Git repository. Use EGit for this purpose!