OTDT/NonAPI

For the sake of a smooth and deep integration into the JDT the OTDT connects to other plugins using some non-API mechanisms. The extent and rationale is documented on this page.

Affected plugins

org.eclipse.jdt.core

The OTDT contains a variant of the jdt.core plugin as described here.

Additionally, the following OT plugins access internals of the JDT/Core:

• org.eclipse.objectteams.otdt
  • OTTypeHierarchies -- This team adapts the TypeHierarchy mechanism to account for implicit inheritance
• org.eclipse.objectteams.otdt.apt
  • VisitorsAdaptor -- This team accesses internal classes for adapting annotation processing (APT)
• org.eclipse.objectteams.otdt.apt
  • Multiple Team classes -- adaptations for the following purposes
    • ensure the incremental builder respects implicit role inheritance as a trigger for rebuilding affected classes
    • make information from aspectBindings available for checking imports and specifically base imports during compilation

org.eclipse.jdt.core.apt

Accessed by:

• org.eclipse.objectteams.otdt.apt
  • VisitorsAdaptor -- This team adapts the AnnotationDiscoveryVisitor so that it will finds annotations of method bindings (callin/callout) and their arguments, too.

org.eclipse.pdt.core

Accessed by:

• org.eclipse.objectteams.otdt.compiler.adaptor
  • PDEAdaptor -- feed information about aspectBindings into the compiler for access checking

org.eclipse.core.resources

Accessed by:

• org.eclipse.objectteams.otdt.compiler.adaptor
  • ResourceProjectAdaptor -- decorate objects of type Project to store two more fields

Status: List of OT-plugins processed:

• org.eclipse.objectteams.otdt
• org.eclipse.objectteams.otdt.apt
• org.eclipse.objectteams.otdt.compiler.adaptor