* Download (Eclipse 4.3) here: http://eclipse.org/downloads/index-developer.php?release=kepler "Eclipse Classic" is a good choice. Also because it is a SDK.

+

* Download (Eclipse 4.3) here: http://eclipse.org/downloads/index-developer.php?release=kepler "Eclipse Classic" is a good choice. Also because it is a SDK. An alternative is RCP. It already includes Egit&Mylyn.

** Developing on a 4.2/Juno SDK will still probably work but we highly recommend using Kepler so we know our code works there.

** Developing on a 4.2/Juno SDK will still probably work but we highly recommend using Kepler so we know our code works there.

** Eclipse 3.x version have not been tested and we do not develop on them.

** Eclipse 3.x version have not been tested and we do not develop on them.

(Optional) "Parallel Tools Platform (PTP) End-User Runtime" - while you will probably check out source to override this, having it installed in the workbench can avert later build problems.

(presume outdated) Note: If you get a java.lang.ClassNotFoundException for org.eclipse.ptp.launch.ui.LaunchConfigurationTab in your target Eclipse install a recent build of this package (B. Watt 2013-02-07).

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 to match the default branch -- or, just use the same name as the server repo)

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.

Also choose what you want the default branch to be (if other than master)

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 (omitting them is optional; you can also just close then later if you like, or just ignore errors), then click Finish. (The tests 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. Omitting them just keeps confusing build errors out of your way.)

Make sure you have set branch.autosetuprebase=always and branch.<name>.rebase=true as described above

This causes a Pull (analogous to a 'cvs update') to do the following:

Fetch

Rebase (It undoes all local commits, fast-forwards the local version to the remote one, and then reapplies the local commits)

Otherwise a Pull only does a Fetch/Merge which causes a spaghetti like history

If new projects have been added to the repository,

Do an Import ... Git > Projects from Git, Next, Choose 'Local', Next, Choose your repository, Next, Next (leave default for 'Import existing projects' and working directory), and on the 'Import Projects' page you should see all the existing projects greyed out, since you already have them in your workspace; make sure all the new projects are checked and hit 'Finish'.

Committing to remote repository

There are two steps to getting code changes in the remote repository at git.eclipse.org: commit then push. (This was a single commit step in CVS. Eclipse Kepler's EGit allows this in a single step via a "Commit and Push" button as well.)

Pull to get the latest changes and prevent errors when you push

right-click on any project in the repository and use Team>Pull

Commit to your local repository - this can be on single files or groups/whole project

right-click on your project and use Team>Commit

If there is a associated bugzilla - copy and paste the title, for example, Bug 400832 - Fix com.ibm.pe.xml attribute from MP_CC_BUF_ATTR to MP_CC_BUF_MEM_ATTR

Push to copy it to the remote repository - do it on project, e.g. from Project Explorer; all commits in your local repository (including other projects) get pushed up to git.eclipse.org

right-click on any project in the repository and use Team>Push to Upstream

Alternatively, you can

Team>Pull (on any project in the repo) first to make sure you've updated, then

Team>Commit and use the checkbox to 'Push the changes to upstream' at the bottom of the 'Commit Changes' dialog.

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"

Copy LML Driver tar file

If you are developing PTP from source in your development workspace and launching into a runtime workspace you also get a similar error to the one above:

TO fix this, install PTP e.g. from ptp-master-xxx or parallel package, and copy this tar file from the eclipse/plugins dir jar file, into the same-name project in your dev workspace.
e.g. from eclipse/plugins/org.eclipse.ptp.rm.lml.da.server_xxx-yyy.jar - unzip that jar file, to find lml-driver.tar and copy that to the plugin project org.eclipse.ptp.rm.lml.da.server

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