Jump to: navigation, search

Difference between revisions of "CDO Source Installation"

Line 41: Line 41:
 
[[Image:Cdo_export_targetdef4.png]]
 
[[Image:Cdo_export_targetdef4.png]]
  
== Bootstrap the Releng Project  ==
+
== Materialize the Sources and the Target Platform ==
  
Now you need to checkout the releng project (Buckminster releng component). Download an appropriate Subversive Team Project Set file:
+
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.
  
{| cellspacing="1" cellpadding="2" border="1" width="200"
+
Then start the Buckminster import wizard:
|-
+
| <br>
+
| Users<br>
+
| Committers<br>
+
|-
+
| 4.1<br>
+
| [http://dev.eclipse.org/svnroot/modeling/org.eclipse.emf.cdo/trunk/plugins/org.eclipse.emf.cdo.releng/psf/bootstrap.psf Download]<br>
+
| [http://dev.eclipse.org/svnroot/modeling/org.eclipse.emf.cdo/trunk/plugins/org.eclipse.emf.cdo.releng/psf/bootstrap-committers.psf Download]<br>
+
|-
+
| 4.0<br>
+
| [http://dev.eclipse.org/svnroot/modeling/org.eclipse.emf.cdo/branches/4.0-maintenance/releng/org.eclipse.emf.cdo.releng/psf/bootstrap.psf Download]<br>
+
| [http://dev.eclipse.org/svnroot/modeling/org.eclipse.emf.cdo/branches/4.0-maintenance/releng/org.eclipse.emf.cdo.releng/psf/bootstrap-committers.psf Download]<br>
+
|-
+
| 3.0<br>
+
| [http://dev.eclipse.org/svnroot/modeling/org.eclipse.emf.cdo/branches/3.0-maintenance/releng/org.eclipse.emf.cdo.releng/psf/bootstrap.psf Download]<br>
+
| [http://dev.eclipse.org/svnroot/modeling/org.eclipse.emf.cdo/branches/3.0-maintenance/releng/org.eclipse.emf.cdo.releng/psf/bootstrap-committers.psf Download]<br>
+
|}
+
 
+
Select File->Import... and choose the Team Project Set import wizard. Select the downloaded bootstrap.psf
+
 
+
'''Hint:''' Instead of downloading the PSF-file, in Indigo you can copy the URL from the table above and import the Team Project Set directly from the copied URL.
+
 
+
[[Image:Cdo install10.png]]
+
 
+
[[Image:Cdo install11.png]]
+
 
+
[[Image:Cdo install12.png]]
+
 
+
<br>
+
 
+
== Materialize the Sources and the Target Platform ==
+
  
To materialize the sources right-click the local.mspec, select Buckminster|Import...
+
[[Image:cdo_import1.png]]
  
[[Image:Cdo_install15.png]]
+
Point it to the Buckminster MSpec of CDO: [http://git.eclipse.org/c/cdo/cdo.git/plain/plugins/org.eclipse.emf.cdo.releng/local.mspec]
  
While the following dialog is running go and fetch a coffee, or two, or three...
+
[[Image: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...
  
[[Image:Cdo_install16.png]]
+
[[Image:cdo_import3.png]]
  
 
Finally hit the 'Finish' button
 
Finally hit the 'Finish' button
  
[[Image:Cdo_install14.png]]
+
[[Image:cdo_import4.png]]
  
 
== Updating the Workspace ==
 
== Updating the Workspace ==

Revision as of 07:05, 4 January 2012

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

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 with re-importing the local.mpec as described above. Then the whole workspace and the target platform are updated.

Note, that re-importing doesn't update your source from the SVN repository. Use Subversive 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.

CDO Versioning Tool.png