'''Hint:''' You may alternatively install from the buckminster update site. Subclipse support is available there. Add '''http://download.eclipse.org/tools/buckminster/updates-3.7''' to your update sites and select the required features.

+

−

+

−

'''Hint:''' If you have trouble with the subversive installation from the indigo update site (e.g. the adapters won't install) try using the subversive update site directly

Select File->Import... and choose the Team Project Set import wizard. Select the downloaded bootstrap.psf

+

The materialization of the workspace contents (sources and binaries) will be performed by Buckminster with the cooperation of EGit and p2.

−

[[Image:Cdo install10.png]]

+

'''Hint:''' The p2 materializer might require lots of memory, and you might experience OutOfMemory Java errors while loading and resolving the target platform. You then might want to make sure your eclipse is configured properly, for instance using (in ''eclipse.ini''):

+

<pre>--launcher.XXMaxPermSize

+

256M

+

-vmargs

+

-Xms512m

+

-Xmx1024m

+

-XX:PermSize=256M

−

[[Image:Cdo install11.png]]

+

</pre>

+

'''For EGit to work properly please create the folder ${user.home}/git on your hard disk.''' (Alternatively you can start your eclipse instance with the following parameter: -Dgit.clone=D:/Development/git/cdo. Also set the default directory und Window-&gt;Preferences--&gt;Team--&gt;Git to "D:/Development/git)

−

[[Image:Cdo install12.png]]

+

Then start the Buckminster import wizard:

−

<br>

+

[[Image:Cdo import1.png]]

−

== Materialize the Sources and the Target Platform ==

+

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 http://git.eclipse.org/c/cdo/cdo.git/plain/plugins/org.eclipse.emf.cdo.releng/local.mspec].

−

To materialize the sources right-click the local.mspec, select Buckminster|Import...

+

For a 4.1 maintenance workspace use [http://git.eclipse.org/c/cdo/cdo.git/plain/plugins/org.eclipse.emf.cdo.releng/local.mspec?h=streams/4.1-maintenance http://git.eclipse.org/c/cdo/cdo.git/plain/releng/org.eclipse.emf.cdo.releng/local.mspec?h=streams/4.0-maintenance] instead. Please note: This does not work until Buckminster [https://bugs.eclipse.org/bugs/show_bug.cgi?id=368573 bug 368573] is resolved (please '''vote''' for the bug!). Instead clone the entire Git repository manually, checkout the maintenance branch, search the workspace for 'local.mspec' and import it by right-clicking and selecting Buckminster-&gt;Import...

−

[[Image:Cdo_install15.png]]

+

[[Image:Cdo import2.png]]

−

While the following dialog is running go and fetch a coffee, or two, or three...

+

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

+

[[Image:Cdo import3.png]]

−

[[Image:Cdo_install16.png]]

+

When the dependencies have been resolved properly hit the 'Finish' button:

−

Finally hit the 'Finish' button

+

[[Image:Cdo import4.png]]

−

[[Image:Cdo_install14.png]]

+

Finally open the ''Preferences'' (Window-&gt;Preferences) and go to the "Target Platform" page. Edit the active target platform and remove the '''location''' (not the target platform definition as a whole!) that points to the running installation. Now you're done.

−

== Updating the Workspace ==

+

== Update 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.

+

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 SVN repository. Use Subversive for this purpose!

+

Note, that re-importing does only '''add''' new source projects but doesn't update existing source projects from the Git repository. Use the 'Pull' command of EGit for this purpose!

Add the API baseline to Eclipse. Open the Preferences (Window->Preferences) and go to the "API Baselines" page:

Click "Add Baseline...". Give it the name CDO 4.1 Baseline and choose the path to the folder on your local disk where you've extracted the downloaded baseline to:

Now the API baseline is created and set active for your workspace:

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.

Hint: The p2 materializer might require lots of memory, and you might experience OutOfMemory Java errors while loading and resolving the target platform. You then might want to make sure your eclipse is configured properly, for instance using (in eclipse.ini):

For EGit to work properly please create the folder ${user.home}/git on your hard disk. (Alternatively you can start your eclipse instance with the following parameter: -Dgit.clone=D:/Development/git/cdo. Also set the default directory und Window->Preferences-->Team-->Git to "D:/Development/git)

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

When the dependencies have been resolved properly hit the 'Finish' button:

Finally open the Preferences (Window->Preferences) and go to the "Target Platform" page. Edit the active target platform and remove the location (not the target platform definition as a whole!) that points to the running installation. Now you're done.

Update 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 does only add new source projects but doesn't update existing source projects from the Git repository. Use the 'Pull' command of EGit for this purpose!