Building AMP from source.

This page just got a lot shorter -- we've completely revamped the AMP build setup using Buckminster, Hudson and Git. Now you can get your entire workspace populated, and install all of your dependencies in a few easy steps! The only thing you need to have is familiarity with the Eclipse IDE and managing update sites. If you want to be up on the absolute latest, experiment with the framework itself, help with documentation, or -- best of all -- create patches and fixes for the project, building from source is the way to go:

  1. Get the latest Eclipse Indigo release. (Use the Modeling release, or just install the SDK and pick the tools you'll need later. You don't need to worry about dependencies themselves, Buckminster handles that for you!)
  2. Install these few features (Help → Install New Software...)
    • Buckminster from: http://download.eclipse.org/tools/buckminster/updates-3.7. (You don't need the Maven feature.)
    • EGit and JGit from the Indigo site Collaboration category. (If you're using Eclipse Modeling download, you'll already have this.)
    • The GEF3D project uses SVN (but not for long!) http://community.polarion.com/projects/subversive/download/eclipse/2.0/indigo-site. You'll need the Buckminster Subversive support as well from the site above.
  3. Import the target platform and workspace.
    • File→Import..→Buckminster→Materialize..
    • In the wizard enter: http://git.eclipse.org/c/amp/org.eclipse.amp.git/plain/releng/org.eclipse.amp.releng/releng/amp-platform.cquery
    • Click Load, wait for that to finish and click Finish.
    • Repeat above steps using: http://git.eclipse.org/c/amp/org.eclipse.amp.git/plain/releng/org.eclipse.amp.releng/releng/amp.cquery
    • Some warnings are expected.

Optional steps recommended for committers and potential contributors:

  1. Create a target platform in your workspace. You'll need to do this before you import your target platform. (The target platform is the set of features needed to build the tool as opposed to the tools needed to develop the tool. There is a difference!)
    • File→New→Other..→General→ Project. Name it "TP"
    • Eclipse→Preferences →Plugin-in Development →Target Platform.
    • Click Add.., Select "Empty", click Next, and then add the TP directory to the new definition. Name it "TP".
    • Don't forget to activate your TP by clicking the checkbox.
  2. If you're planning on committing code at some point (you know who you are!) don't forget to change the git push settings to configure git in preferences and change your push configuration to use ssh.

To try out your source build, just create an Eclipse Application. See the Eclipse documentation for more information.

  1. Select Run → Run Configurations..
  2. Select Eclipse Application and click "New Launch Configuration".
  3. The default "All Workspace and Enabled Target Plugins.." option is fine. If you want to specify individual plugins, you will probably need at least:
    • org.eclipse.amp.amf.ide
    • org.eclipse.amp.escape.amf.ide
    • org.eclipse.amp.amf.ide
    • org.eclipse.amp.amf.data.editor
    • org.eclipse.amp.amf.paramters.ui
    • org.eclipse.amp.amf.testing.ide
    • org.eclipse.sdk
    Then, select the "Add Required Plugins" button.
  4. Click the Run button.
  5. A new Eclipse application should launch. Note that you can also launch using the Debugger which is helpful for debugging issues with AMP models.

Problems? Send a note to the amp-developer list or our newsgroup.