Eclipse troubleshooting

  • Tier: Free, Premium, Ultimate
  • Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
  • Status: Experiment
This page contains information related to upcoming products, features, and functionality. It is important to note that the information presented is for informational purposes only. Please do not rely on this information for purchasing or planning purposes. The development, release, and timing of any products, features, or functionality may be subject to change or delay and remain at the sole discretion of GitLab Inc.

If the steps on this page don’t solve your problem, check the list of open issues in the Eclipse plugin’s project. If an issue matches your problem, update the issue. If no issues match your problem, create a new issue.

Review the Error Log

  1. In the menu bar of your IDE, select Window.
  2. Expand Show View, then select Error Log.
  3. Search for errors referencing the gitlab-eclipse-plugin plugins.

Locate the Workspace Log file

The Workspace log file, named .log is located in the directory <your-eclipse-workspace>/.metadata.

Enable GitLab Language Server debug logs

To enable GitLab Language Server debug logs:

  1. In your IDE, select Eclipse > Settings….
  2. On the left sidebar, select GitLab.
  3. In Language Server Log Level, enter debug.
  4. Select Apply and Close.

The debug logs are available in the language_server.log file. To view this file, either:

  • Go to the directory /Users/<user>/eclipse/<eclipse-version>/Eclipse.app/Contents/MacOS/.gitlab_plugin, replacing <user> and <eclipse-version> with the appropriate values.
  • Open the Error logs. Search for the log Language server logs saved to: <file>. where <file> is the absolute path to the language_server.log file.

Certificate errors

You may experience errors connecting to GitLab if you connect to GitLab through a proxy or using custom certificates. Support for HTTP proxies and support for custom certificates are proposed for a future release.