Difference between revisions of "OTDevelopmentSetup"

Revision as of 15:31, 8 November 2016

For hacking on the OTDT the following steps should get you going. Note that headless build and steps for a release are described at OTBuilding.

To work on the current master of Object Teams, you may need the latest development build.

When using a an older IDE, consider switching to the corresponding maintenance branch from the OT git repo.

Install a matching version of the OTDT into the above
Consider also installing the corresponding source feature, for lookup of source code for plugins which you don't have in your workspace
Install EGit
Simple checkout
- OTDT: download http://git.eclipse.org/c/objectteams/org.eclipse.objectteams.git/plain/releng/map/otdt.psf, and import via Import > Team > Team Project Set
- Tests: download http://git.eclipse.org/c/objectteams/org.eclipse.objectteams.git/plain/releng/map/otdt-all-tests.psf, and import via Import > Team > Team Project Set (long running operation)
Manual checkout (alternative if you need more control than "simple checkout")
- Clone this repo: http://git.eclipse.org/c/objectteams/org.eclipse.objectteams.git
- Check out projects from git:
  - Minimally:
    - org.eclipse.jdt.core
  - For the full OTDT add:
    - all projects under plugins/
  - For tests add
    - org.eclipse.jdt.core.tests.compiler
    - org.eclipse.jdt.core.tests.model
    - all projects under testplugins
    note that tests have dependencies on further test projects from JDT and related, which are hosted in their respective repositories.
    
    TODO collect minimal set of references, maybe some full zip of dependent test projects
  - For interactive deployment add
    - all projects under features/

compile: Since installing the OTDT already provides all dependencies, compiling in the IDE should work out of the box.

create jars for the runtime environment using these jar descriptions (will appear in org.eclipse.objectteams.otdt/lib):
- org.eclipse.objectteams.runtime/otre_min.jardesc
- org.eclipse.objectteams.otre/otre_agent.jardesc
- org.eclipse.objectteams.otredyn/otre_agent.jardesc

deploy / export plug-ins and features: Use the wizard Export > Plug-in Development > Deployable features and select these features:

org.eclipse.objectteams.otdt -- the umbrella feature for the IDE
org.eclipse.objectteams.otdt.core.patch -- patch feature containing the OT/J version of JDT/Core
org.eclipse.objectteams.otequinox -- OT/J runtime and integration for Equinox

building the command line compiler: You may simply use the org.eclipse.jdt.core_3.X.Y.v_OTDT_abc.jar produced by the above export.

Alternatively, for building the minimal ecotj.jar run org.eclipse.jdt.core/scripts/export-ecj.xml as Ant Build.

test: There are lots of individual JUnit suites, and aggregate suites, typically called s.t. like TestAll.

The central suite for OT/J is org.eclipse.objectteams.otdt.tests.otjld.AllTests
Each test suite can be invoked using Run As ... > JUnit Plug-in Test
For those tests not including any UI test launch can be optimized on the Main tab of the launch configuration by selecting Program to Run > Run an application > [No Application] - Headless Mode

projects and dependencies: The full list of plug-ins and features including dependencies can be found in /releng/map/otdt.map

@@ Line 1: / Line 1: @@
 For hacking on the [[Object_Teams_Development_Tooling|OTDT]] the following steps should get you going. Note that headless build and steps for a release are described at [[OTBuilding]].
-* Install a recent Eclipse SDK
+* Install a recent Eclipse Package (recommended IDE for Committers).
+: To work on the current master of Object Teams, you may need the latest development build.
+: When using a an older IDE, consider switching to the corresponding maintenance branch from the OT git repo.
 * Install a matching version of the OTDT into the above
 *: Consider also installing the corresponding source feature, for lookup of source code for plugins which you don't have in your workspace