Skip to main content
Jump to: navigation, search


Revision as of 09:01, 26 June 2012 by (Talk | contribs) (History)

Selected Facts regarding OT/J and the OTDT


2001 Development of Lua Aspectual Components (LAC), a prototypical predecessor of Object Teams
Late 2001 Start of the implementation of compiler & runtime environment for OT/J
2003 Start of the Eclipse based re-implementation of the compiler (based on Eclipse 2.1.1)
2003-2006   Funding by the German Research Ministry (project TOPPrax)
2005 First public presentation of the OTDT at AOSD'05 in Chicago (version 0.7.5 based on Eclipse 3.0)
2006 First plugins written using OT/Equinox
2007 Version 1.0.0 of the OTDT (based on Eclipse 3.2) and version 1.0 of the OTJLD
2008 Version 1.2.0 of the OTDT (based on Eclipse 3.4)
2009 Version 1.3.0 of the OTDT (based on Eclipse 3.5)
Jan 2010 Eclipse Object Teams Project created, started to move content and infra structure to
Mar 2010 Version 1.4.0 of the OTDT (based on Eclipse 3.6M6) — final release from
Jul 2010 Version 0.7.0 (incubation) of the OTDT (based on Eclipse 3.6) — first release from
Jun 2011 Version 2.0.0 of the OTDT (part of the Indigo Release Train) — Project Graduation
Jun 2012 Version 2.1.0 of the OTDT (part of the Juno Release Train)


  • Andreas Kaiser
  • Carsten Pfeiffer
  • Christine Hering
  • Christine Hundt
  • Gregor Brcan
  • Jan Wloka
  • Jaroslav Svacina
  • Joachim Hänsel
  • Johannes Gebauer
  • Jürgen Widiker
  • Karsten Meier
  • Marco Mosconi
  • Markus Witte
  • Michael Krüger
  • Olaf Otto
  • Ralf Anklam
  • Sascha Kolewa
  • Stephan Herrmann

And valuable feedback from many more.

Implementation Figures

327 specific error messages (as of version 2.0.0)
The compiler supports 327 dedicated error or warning messages that precisely explain any problem that the compiler has identified in your sources. Each message refers to the paragraph in the OTJLD that is being violated by the problem at hand. The Problems view of the OTDT furthermore offers an option "Go To Language Definition" in its context menu for quickly navigating to this exact paragraph for further reference.
  • 0.7.0: 314
10 OT/Equinox plug-ins (as of version 2.0.0)
  • 10 Plugins of the OTDT are built using the OT/Equinox technology for adapting existing plugins. These OT/Equinox plugins comprise
  • 77 team classes
  • 215 bound role classes
  • 286 callin bindings
  • 265 callout bindings
  • approx. 35,900 PSLOC (physical source lines of code)
  • the following plug-ins are adapted by the above:
  • org.eclipse.core.resources
  • org.eclipse.debug.core
  • org.eclipse.debug.ui
  • org.eclipse.jdt.apt.core
  • org.eclipse.jdt.core (incl. fragment org.eclipse.jdt.compiler.apt)
  • org.eclipse.jdt.debug
  • org.eclipse.jdt.debug.ui
  • org.eclipse.jdt.junit
  • org.eclipse.jdt.junit.core
  • org.eclipse.jdt.launching
  • org.eclipse.jdt.ui
  • org.eclipse.jface
  • org.eclipse.jface.text
  • org.eclipse.pde.core
  • org.eclipse.pde.ui
  • org.eclipse.pde.launching
  • org.eclipse.ui.workbench
  • 0.7.0:
    • 8 OT/Equinox plug-ins
    • 77 team classes
    • 206 bound role classes
    • 280 callin bindings
    • 258 callout bindings
    • approx. 19,400 PSLOC

Test Figures

The initial development of compiler and runtime was driven by a test suite of 699 JACKS test cases (2004). This suite has continuously grown and was later converted into a suite of JUnit Plug-in tests. As of June 2011 this suite comprises 2412 unique JUnit tests (part of the tests are executed twice - for different compliance levels, so the total number of tests executions currently if 4550).

For the development of the OTDT original JDT JUnit Plug-in tests are run to check for regressions amounting to 44385 JUnit tests. Additionally, 2367 JUnit tests have been developed specifically for the OTDT.

Thus a full test run currently comprises 51302 tests.

Back to the top