From ArchWiki
Revision as of 11:28, 28 May 2012 by Plpbeta (talk | contribs)
Jump to: navigation, search

This template has only maintenance purposes. For linking to local translations please use interlanguage links, see Help:i18n#Interlanguage links.

Local languages: Català – Dansk – English – Español – Esperanto – Hrvatski – Indonesia – Italiano – Lietuviškai – Magyar – Nederlands – Norsk Bokmål – Polski – Português – Slovenský – Česky – Ελληνικά – Български – Русский – Српски – Українська – עברית – العربية – ไทย – 日本語 – 正體中文 – 简体中文 – 한국어

External languages (all articles in these languages should be moved to the external wiki): Deutsch – Français – Română – Suomi – Svenska – Tiếng Việt – Türkçe – فارسی

Eclipse is an open source community project, which aims to provide a universal development platform. The Eclipse project is most widely known for its cross-platform integrated development environment (IDE). The Arch Linux packages (and this guide) relate specifically to the IDE.

The Eclipse IDE is largely written in Java but can be used to develop applications in a number of languages, including Java, C/C++, PHP, Python and Perl. The IDE can also provide subversion support (see below) and task management (either through its built-in TODO list or through the eclipse-mylyn package).


It is very easy to install the Eclipse SDK in Arch Linux:

# pacman -S eclipse

This base package has Java development support built in.


There are two methods to install plugins for Eclipse:

  • using pacman to install plugins packaged in Arch repositories (see Eclipse plugin package guidelines for further informations);
  • using Eclipse's plugin manager to download and install plugins from their original repositories; in this case you have to find the needed repository in the plugin's website, then go to Help -> Install New Software..., enter the repository in the Work with field, select the plugin to install from the list below and follow the instructions.
  • If you install plugins with Eclipse's plugin manager, you are advised to launch Eclipse as root: this way the plugins will be installed in /usr/share/eclipse/plugins/; if you installed them as normal user, they would be stored in a version-dependent folder inside ~/.eclipse/, and, after upgrading Eclipse, they wouldn't be recognized any longer.
  • Do not use Eclipse as root for your everyday work.

C/C++ support

Eclipse CDT

Perl support


PHP support

Eclipse PDT


Aptana PHP

See Aptana Studio further down.

Python support


Web development (HTML, CSS, JavaScript...)

Aptana Studio

Subversion support


Eclipse Subversive

Git support


Mercurial support


LaTeX support



  • Eclipse and the plugins installed with pacman are obviously updated with pacman itself.
  • For plugins installed with Eclipse's plugin manager, run Eclipse and select Help -> Check for Updates (if you have installed them as root as advised in the section above, you have to run Eclipse as root).

For plugins to be updated, you should check to have their update repositories enabled in Window -> Preferences -> Install/Update -> Available Software Sites: you can find each plugin's repository(es) on the respective project website. To add, edit, remove... repositories just use the buttons on the right of the Available Software Sites panel. For Eclipse 3.7 (Indigo), check you have enabled this repository:

To receive update notifications, go to Window -> Preferences -> Install/Update -> Automatic Updates. If you want to receive notifications for plugins installed as root, you should run Eclipse as root, go to Window -> Preferences -> Install/Update -> Available Software Sites, select the repositories related to the installed plugins and Export them; then run Eclipse as normal user and Import them in the same panel.

Using Sun JDK in place of OpenJDK

Tango-inaccurate.pngThe factual accuracy of this article or section is disputed.Tango-inaccurate.png

Reason: please use the first argument of the template to provide a brief explanation. (Discuss in Talk:Eclipse#)

Eclipse depends on openjdk6 by default, which you can easily replace with jdk, following this article.

By the way, you may want to link the file /opt/java/bin/java to /usr/bin/java:

# ln -s /opt/java/bin/java /usr/bin

Enable javadoc integration

Want to see API entries when hovering the mouse pointer over standard Java methods?

Online Version

If you have constant internet access on your machine, you can use the on-line documentation provided by sun. Just follow these instructions:

  1. Go to Window/Preferences, then go to Java/Installed JREs.
  2. There should be one named "java" with the type "Standard VM". Select this and click Edit.
  3. Select the /opt/java/jre/lib/rt.jar item under "JRE system libraries:", then click "Javadoc Location...".
  4. Enter "" in the "Javadoc location path:" text field.
  5. Done!

Offline Version

If you have no internet connection on your development machine or do not want to constantly consume bandwidth for the documentation, you can store the documentation locally, by installing the openjdk[version]-src package. Eclipse should find the javadocs automatically.


Autocompletion and javadoc render crash

For some reason, libxul may crash Eclipse with a Traceback like

# Problematic frame:
# C  []  NS_InvokeByIndex_P+0x5e9a

To fix this issue, you can try installing libwebkit and adding the following lines in your /usr/share/eclipse/eclipse.ini:


If that does not work (or if you do not want to use libwebkit) try this:

1. Download
2. Unpack it into /home/<Username>/.xulrunner (or another location)
3. Add this line to your Eclipse configuration file /usr/share/eclipse/eclipse.ini:
Now everything should just work fine and tooltips should display correctly.

Crash on first boot or when choosing "Help->Welcome"

See above.