Choose the branches you want to clone (usually ptp_6_0 and master==HEAD) and click Next >.

Note: all workspaces on your machine that talk to this local clone of the repository will all use the same branch at a time. You may want separate clones of the repo (one for each release/branch) for this reason. If so, the last page of the wizard lets you specify a different directory for this clone and you don't have to use same name as remote repo name for your directory.

One convention for this: Make two clones of the git repo, one for master (Kepler work) and one for the ptp_6_0 branch (Juno work). You can put both branches in each clone.

One set of suggested names of the repos:

Set of repos where 'master' is the (default) branch used - for Kepler work (that is, name the repo the same as the remote repo name)

Click Next> to choose where you want the repository located locally. It can be anywhere. See suggested names above if you don't have a better idea.

Click Finish. The repository should be downloaded.

Once the repository has downloaded you should see it in the list. Select it.

If you have already cloned the repository, and it isn't shown in the list (e.g. Clone done from another workspace)

Select Add... and add it.

You should now see it in the list. Select it.

Click Next> then Next> again and you should see a list of all the projects.

Select all of the projects except the following, then click Finish:

org.eclipse.ptp.rdt.core.tests

org.eclipse.ptp.rdt.sync.rsync.core

org.eclipse.ptp.rdt.sync.rsync.ui

org.eclipse.ptp.rdt.ui.tests

(The rsync projects are not included in the PTP build and currently do not compile. The other two projects are unit tests for RDT; to compile and run them, you would need to check out the source code for CDT's unit testing projects and their dependencies.)

API baseline and code formatter

Building runtime binary

(This is only true of the older resource managers that require a proxy on the target machine. Not needed for most recent resource managers now.)

To e.g. run with a resource manager, you may have to build some platform-specific binary/proxy code.
For example, to run with OpenMPI locally on MACOSX, cd to the org.eclipse.ptp.macosx.x86 project in a terminal window, and execute

sh BUILD

This should build the executable 'sdm' in the bin/ directory. Do not be alarmed if you see "LoadLeveler not installed, skipping..." etc - if you do not have these IBM components installed on your system, there is no need for it to build those binaries.

Copy Remote Tools Dstore server jar

If you are using Remote Tools ... you may see the error "Unable to locate payload "rdt-server.jar" in bundle "org.eclipse.ptp.rdt.server.dstore" "
when you launch a runtime workspace and make a (purely) remote project.

So you must do the following (Until we can build rdt server jar here) ...
From a PTP (end-user) installation, unzip eclipse/plugins/org.eclipse.ptp.rdt.server.dstore_xxx.jar into a directory.
Then from the unzipped contents
move rdt-server.jar to your development workspace project: org.eclipse.ptp.rdt.server.dstore

(This is the file that will be moved up to the remote host location when you create a remote project. Remote Tools installs this jar on the server automatically and starts it for you.)

If you don't, you will see the error popup "Unable to locate payload "rdt-server.jar" in bundle "org.eclipse.ptp.rdt.server.dstore"

Launching a runtime workbench running the code you checked out into your workspace

Run > Debug Configurations ...

Double-click on 'Eclipse Application' - or click and click on the 'new' icon

Defaults are probably ok to run with all the plugin projects in your workspace; hit 'Debug' in lower right corner