• Eclipse Update Manager
  The mojax tools may be installed into the Eclipse platform using the Eclipse Update Manager.

Troubleshooting

If you experience trouble with the Mojax plugin, please follow the steps below to narrow down the problem. Once you have gathered the necessary information, visit the Mojax discussion group on Yahoo to search for and/or post a question about the problem.

Collect configuration information

To troubleshoot the problem, we will need as much information as possible. Following is a list of information that will be of great help in tracking down the issue:

• Version number of Eclipse that you are running. Select Help / About Eclipse Platform and note the Version and Build information.
• Version number of the mojax plugin. From the About Eclipse Platform dialog, press the Feature Details button and note the version of the mojax feature.
• The platform mojax is being run on, such as Windows XP (c) or Debian Linux.
• The windowing system mojax is running on, such as Windows XP (c), GTK or Motif.
• Manufacturer and version number of the JDK you are using. (e.g. Sun JDK 1.4.2_03)

Create a detailed description of how to reproduce the problem

• Provide a step-by-step description of how to reproduce the problem.
• Describe in as much detail as possible any error messages that occur.
• If you have changed any Preference settings, please provide information on the changes.

Include the workspace log file

Eclipse stores settings and other state information in your workspace. By default, your workspace is stored in the directory named workspace within your Eclipse installation directory.

Within the workspace directory, there is a subdirectory named .metadata. This, in turn, may contain a file named .log. Unix users, remember that files beginning with the character "." are hidden by default. You will need to use the -a option of the ls command in order to see the .log file in a directory listing.

The .log file contains valuable debugging information, particularly exception traces. One way to help isolate a problem is to close Eclipse, delete this file, then restart Eclipse. From here, run through the steps to recreate the error, then close Eclipse again. Now look to see if a .log file has been created. If it has, include the contents of this file as part of your report when posting a question on the Mojax forum (as described above). (NOTE: If the contents of this file are particularly large, you may want to work out other arrangements for delivery to mFoundry rather than sending it directly to the group.)

If you have the Plugin Development Environment loaded, this same information can be more easily obtained by opening the Error Log view.