This page last changed on Feb 09, 2009 by stepheneb.

Setup Development Environment

The current version of this document assumes you are running an up-to-date version of Mac OS X 10.5.

At the end are some notes on OS-specific adaptations.

1. Install up-to-date Apple Developer Tools

Make sure you have an up-to-date install of the Apple Developer Tools.

You can download Apple Developer Tools by registering for a free account Apple Developer Connection account here: The download is about 1GB.

Apple Developer Tools installs the gcc toolchain.

2. Install MacPorts

Installing macports will allow you to easily install many unix applications adapted or configured for building on MacOS X.

You can download macports here:

Now, make sure that the /opt/local/bin/port exists. Add /opt/local/bin to your path if it does not exist.

go to the terminal and run:

sudo port -v selfupdate
sudo port install wget

3. Add /usr/local/bin to your path

Many development tools are installed in the directory /usr/local/bin and this path should be added to the beginning of your PATH environmental variable.

Create the directory /usr/local/bin if it doesn't already exist:

sudo mkdir -p /usr/local/bin

the -p option to mkdir creates the complete dir path specified if it doesn't exist

If you use bash you can add this to your PATH environmental variable in either your /.bash_profile or /.bash_rc files with a statement like his:

export PATH=/usr/local/bin:$PATH

this adds the path /usr/local/bin to the beginning of any existing $PATH variable

4. Install Subversion 1.5.x

Binary distributions of Subversion for MacOS are available here:

5. Install git

Git is a distributed version control system (DVCS) which is much faster than subversion. In addition when using git you have a complete history of the repository cloned to your local hard drive. This means you can use local tools like gitk to easily browse all the recent changes in a repository without making network connections back to the main subversion repository.

At this point only the otrunk-examples code is available as a git repository.

See: Installing git with macports.

6. Install Maven 2.0.6 (or newer)

Check what version of maven may already be installed:

$ mvn --version
Maven version: 2.0.9
Java version: 1.5.0_16
OS name: "mac os x" version: "10.5.5" arch: "i386" Family: "unix"

You can download maven here:

Create an .m2 dir in your home dir:

mkdir ~/.m2

7. Install Eclipse

The best option seems to be to get Eclipse IDE for Java EE Developers If you aren't doing web development so this will be a little bit extra. However it is really useful to have the javascript and xml editors which you get with this

8. Install Eclipse Plugins

The first two plugins in this list are required, the third which enables Eclipse integration with git is not necessary at this point however we will be integrating development at CC with a distributed VCS system in the near future and git seems the mostly likely candidate.

Subversion - subclipse plugin

Maven 2 - m2eclipse plugin

Git - egit plugin

9. Import CC Eclipse project set and checkout code

Download this eclipse project set file:

  • Then in eclipse go to File, Import...
  • In the team folder of the Import dialog, select "Team Project Set"
  • Use the OTrunkProjectSet.psf file you just downloaded.

Importing all the projects transfers over 1GB so be sure you are on a high-speed connection.

This project set includes all of the Concord OTrunk work as well as the Concord simulations (MW) and some external simulations (PHET). In addition the MozSwing project hosted at sourceforge is included.

This project set also includes working sets to help organize the projects in Eclipse Package Explorer

10. Enable Working Sets in Eclipse

  1. In Package Explorer configure Top Level Elements to show Working Sets.
  2. Then in Package Explorer select Configure Working Sets and make all the working sets active.

Use the small triangle in the top-left corner of the Package Explorer pane in Eclipse.

11. Automatic ssh-agent startup for shell users

If you will be committing code to CC repositories or making changes on servers setup an automatic ssh-agent startup when you open a shell session. Automatic ssh-agent startup for shell users.

12. Operating System Notes

Windows Notes

Mac OS X Notes

Linux Notes

  • nothing here yet ...
Document generated by Confluence on Jan 27, 2014 16:52