This is an Archived Page

Please see the new version at Eclipse.org

Trouble Shooting -- Error messages, causes and solutions

This page collects error messages of the ObjectTeamsDevelopmentTooling that may pop up in dialogs and/or appear in the log file at {$workspace_loc}/.metadata/.log, along with explanations of root causes and possible solutions.

Issues specific to Mac OS are being collected on page OtdtOnMac.

Issues specific to milestones prior to the 1.3.0 release have been collected on page TowardsOTDT1.3.

  • Error message:
    OT/Equinox: Required fragment org.eclipse.jdt.compiler.apt has no host bundle (aspect binding of org.objectteams.otdt.apt.adaptor)
    Cause:
    The plugin org.objectteams.otdt.apt.adaptor tries to adapt the bundle fragment org.eclipse.jdt.compiler.apt, which requires an execution environment JavaSE-1.6. On platforms where JavaSE-1.6 is not available (like, e.g., MacOSX) this fragment cannot be resolved, which in turn causes the adaptor plugin to fail, too.
    Solution:
    No action required.
  • Exception:
    org.eclipse.jdt.internal.compiler.problem.AbortCompilation
    Cause:
    This exception likely signals an incomplete classpath. In some cases the problem view will give further information by specifying a specific type that could not be resolved.
    Solutions:
    Some occurrences of this exception are harmless. Only if this exception is paired with other unexpected behavior it might be a hint to the underlying root cause.
  • Exception:
    org.eclipse.debug.core.DebugException: org.eclipse.jdi.TimeoutException: Timeout occurred while waiting for packet 12345
    Cause:
    Even if reported by org.objectteams.otdt.debug this exception is most certainly not caused by the OTDT but by the underlying debugger or the VM.
    Solutions:
    If using a different VM is an option this could actually help. Otherwise there's little we could recommend here.
  • Exception:
    No OT/J plug-in project found, debug functionality not fully available.
    Cause:
    An eclipse application (or JUnit plugin test) was launched in debug mode, while no project with OTJavaNature was open in the workspace. As the only result of this problem the team monitor view will not work.
    Solution:
    Open any project that has the OTJavaNature.
  • Exception:
    Unable to create editor ID org.objectteams.otdt.ui.OTJavaEditor: No editor descriptor for id org.objectteams.otdt.ui.OTJavaEditor
    Cause:
    The workspace was last opened with an OTDT < 1.3.0.200905161144 and some java editors were open at that time using OTJavaEditor as the implementation. In newer versions of the OTDT OTJavaEditor is obsolete because we now directly adapt the standard JavaEditor.
    Solution:
    Close all java editors once. Newly opened editors will use the new implementation (JavaEditor plus adaptation).
  • Exception:
    java.lang.ClassCircularityError: org/eclipse/jface/dialogs/IDialogSettings
    Cause:
    When this happens in an OT/Equinox project, it could mean that you are trying to combine the following two elements
    • Define an aspectBinding to bundle org.eclipse.ui.workbench
    • Define an activator that extends org.eclipse.ui.plugin.AbstractUIPlugin
  • In this situation we get the following cyclical dependencies:
    1. when starting org.eclispe.ui.workbench the adapting team must be instantiated and activated
    2. when instantiating the team its bundle must be activated using the activator
    3. when loading the activator class AbstractUIPlugin must be loaded
    4. org.eclipse.ui.workbench must be started

More complex structures may occurr when the aspect bundle adapts another bundle, which has an activator extending AbstractUIPlugin. This could also cause the ClassCircularityError.

Workaround:
For the simple variant just split the bundle into two, to make the activator independent of the aspect bundle.