Difference between revisions of "Eclipse"

From ArchWiki
Jump to navigation Jump to search
(spanish interlanguage link)
m (Added rust to the "including" list)
 
(18 intermediate revisions by 5 users not shown)
Line 4: Line 4:
 
[[ja:Eclipse]]
 
[[ja:Eclipse]]
 
[[ru:Eclipse]]
 
[[ru:Eclipse]]
 +
[[pt:Eclipse]]
 
[[zh-hans:Eclipse]]
 
[[zh-hans:Eclipse]]
[https://eclipse.org 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.
+
[https://eclipse.org Eclipse] it is an open source community project aimed at providing a universal development platform. The Eclipse project is best known for its multiplatform integrated development environment (IDE). Arch Linux packages (and this guide) are specifically related 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, Perl and Python. The IDE can also provide subversion support and task management.
+
Eclipse IDE is largely written in Java, but can be used to develop applications in many languages, including Java, C / C++, PHP, Perl, Rust and Python. The IDE can also provide subversion support and task management.
  
 
== Installation ==
 
== Installation ==
Line 18: Line 19:
 
* {{Pkg|eclipse-php}} for PHP Developers
 
* {{Pkg|eclipse-php}} for PHP Developers
 
* {{Pkg|eclipse-javascript}} for JavaScript and Web Developers
 
* {{Pkg|eclipse-javascript}} for JavaScript and Web Developers
 +
* {{Pkg|eclipse-rust}} for Rust Developers
  
You cannot install multiple of these at the same time since they conflict, see {{Bug|45577}}: choose the package above which most immediately fulfills your needs, and then add support for any additionally required languages through [[#Plugins]].
+
You cannot install several of them at the same time as they conflict, see {{Bug|45577}}: choose the package above which meets your needs immediately and add support for the additional languages you need through [[#Plugins]].
  
 
== Plugins ==
 
== Plugins ==
  
Many plugins are easily installed using '''pacman''' (see [[Eclipse plugin package guidelines]] for further information). This will also keep them up-to-date. Alternatively, you can choose either the [[#Eclipse Marketplace|Eclipse Marketplace]] or the internal [[#Plugin manager|plugin manager]].
+
Many plugins are easily installed using '''pacman''' (look [[Eclipse plugin package guidelines]] for more information). This will also keep them updated. Alternatively, you can choose the [[#Eclipse Marketplace|Eclipse Marketplace]] or the internal [[#Plugin manager|plugin manager]].
  
 
=== Add the default update site ===
 
=== Add the default update site ===
  
Make sure that you check that the default update site for your version of Eclipse is configured so that plugin dependencies can automatically be installed. The most current version of Eclipse is Photon and the default update site for it is: http://download.eclipse.org/releases/photon. Go to Help > Install new Software > Add, fill the name to easily identify the update site later - for instance, Photon Software Repository - and fill the location with the url.
+
Be sure to verify that the default update site for your version of Eclipse is configured so that plug-in dependencies can be installed automatically. The most current version of Eclipse is Photon and the default update site is: http://download.eclipse.org/releases/photon. Go to ''Help > Install New Software > Add'', fill in the name to easily identify the update site later - for example, Photon Software Repository - and fill in the location with the URL.
  
 
=== Eclipse Marketplace ===
 
=== Eclipse Marketplace ===
  
 
{{Note|make sure you have followed the [[#Add the default update site|Add the default update site]] section.}}
 
{{Note|make sure you have followed the [[#Add the default update site|Add the default update site]] section.}}
To use the Eclipse Marketplace, install it first: go to Help > Install new software > Switch to the default update site > General Purpose Tools > Marketplace Client. Restart Eclipse and it will be available in Help > Eclipse Marketplace.
+
To use the Eclipse Marketplace, install it first: go to ''Help > Install new software > Switch to the default update site > General Purpose Tools > Marketplace Client''. Restart Eclipse and it will be available in ''Help > Eclipse Marketplace''.
  
 
=== Plugin manager ===
 
=== Plugin manager ===
Line 77: Line 79:
 
# Go to ''Window > Preferences'', then go to ''Java > Installed JREs''.
 
# Go to ''Window > Preferences'', then go to ''Java > Installed JREs''.
 
# There should be one named "java" with the type "Standard VM". Select this and click ''Edit''.
 
# There should be one named "java" with the type "Standard VM". Select this and click ''Edit''.
# Select the {{ic|/opt/java/jre/lib/rt.jar}} item under "JRE system libraries:", then click ''Javadoc Location...''.
+
# Select the {{ic|/usr/lib/jvm/java-8-openjdka/jre/lib/rt.jar}} item under "JRE system libraries:", then click ''Javadoc Location...''.
 
# Enter "https://docs.oracle.com/javase/8/docs/api/" in the "Javadoc location path:" text field.
 
# Enter "https://docs.oracle.com/javase/8/docs/api/" in the "Javadoc location path:" text field.
  
Line 92: Line 94:
 
=== Dark theme ===
 
=== Dark theme ===
  
Eclipse supplies a Dark theme which can be enabled in Window > Preferences > General > Appearance and selecting the 'Dark' theme.
+
Eclipse supplies a Dark theme which can be enabled in ''Window > Preferences > General > Appearance'' and selecting the ''Dark'' theme.
  
The dark theme uses its own colours rather than the GTK theme colours, if you prefer it to fully respect GTK colour settings, then remove or move to backup sub folder all of the .css files from {{ic|/usr/share/eclipse/plugins/org.eclipse.ui.themes_1.0.0.xxxx/css/}}.
+
The dark theme uses its own colours rather than the GTK theme colours, if you prefer it to fully respect GTK colour settings, then remove or move to backup sub folder all of the .css files from {{ic|/usr/lib/eclipse/plugins/org.eclipse.ui.themes_''version''/css/}}, replacing the {{ic|''version''}} with the appropriate version number.
  
 
=== Change Default Window Title Font Size ===
 
=== Change Default Window Title Font Size ===
  
You cannot change the window title font size using the Eclipse preferences, you must edit the actual theme .css files. Note, that you will have to redo this when you upgrade eclipse.
+
You cannot change the window title font size using the Eclipse preferences, you must edit the actual theme .css files. These are located under {{ic|/usr/lib/eclipse/plugins/org.eclipse.themes_''version''/css/}} directory, where {{ic|''version''}} is the actual theme version number.
They are located under
+
 
/usr/share/eclipse/plugins/org.eclipse.platform_4.3.<your version number>/css
+
Use an [[text editor]] to edit the appropriate file, e.g. {{ic|e4_default_gtk.css}} if you are using the "GTK theme".
Open the appropriate file with your text editor, ie e4_default_gtk.css if you are using the "GTK theme".
+
 
Search for .MPartStack, and change the font-size to your desired size
+
In this file, search for {{ic|.MPartStack}}, and change the font-size to your desired size:
 +
 
 
  .MPartStack {
 
  .MPartStack {
 
         font-size: 9;
 
         font-size: 9;
Line 109: Line 112:
 
  }
 
  }
  
=== Disable GTK+ 3 ===
+
{{Note|This needs to be redone whenever eclipse is upgraded.}}
 +
 
 +
=== Disable GTK 3 ===
 +
 
 +
If the SWT GTK 3 UI gets buggy or unusable, it can be disabled by prepending {{ic|1=SWT_GTK3=0}} [[environment variable]] when starting Eclipse:
  
When the SWT GTK+ 3 UI is buggy and sometimes unusable, You can try to disable the use of GTK+ 3 with the SWT_GTK3=0 [[environment variable]] when you start eclipse:
 
 
  SWT_GTK3=0 eclipse
 
  SWT_GTK3=0 eclipse
  
Another option to achieve the same effect is to add the following to {{ic|/usr/lib/eclipse/eclipse.ini}}.
+
Another option to achieve the same effect is to add the following to Eclipse's ini file, '''before''' {{ic|--launcher.appendVmargs}}:
--launcher.GTK_version
 
2
 
  
Those two lines must be added '''before''':
+
{{hc|/usr/lib/eclipse/eclipse.ini|
--launcher.appendVmargs
+
--launcher.GTK_version
 +
2
 +
}}
  
 
=== Freshplayerplugin ===
 
=== Freshplayerplugin ===
Line 133: Line 139:
  
 
=== Show in System Explorer does not work ===
 
=== Show in System Explorer does not work ===
See [http://help.eclipse.org/luna/index.jsp?topic=%2Forg.eclipse.platform.doc.user%2Freference%2Fref-9.htm&cp=0_4_1_52 this] guide. Go to '''Window''' > '''Preferences''' > '''General''' > '''Workspace''' and change the command launching system explorer. As Xfce user you may like to change it to {{ic|thunar ${selected_resource_uri} }} to open the selected folder with thunar.
+
 
 +
See [http://help.eclipse.org/luna/index.jsp?topic=%2Forg.eclipse.platform.doc.user%2Freference%2Fref-9.htm&cp=0_4_1_52 this] guide. Go to ''Window > Preferences > General > Workspace'' and change the command launching system explorer. As [[Xfce]] user you may like to change it to {{ic|thunar ${selected_resource_uri} }} to open the selected folder with thunar.
  
 
=== Display issues under Wayland ===
 
=== Display issues under Wayland ===
 +
 
When running Eclipse on Wayland, you may encounter rendering issues such as slow response time to mouse events or chopped dialog windows (Bug report [https://bugs.eclipse.org/bugs/show_bug.cgi?id=483545]). A possible workaround for this issue is to force Eclipse to run under XWayland.
 
When running Eclipse on Wayland, you may encounter rendering issues such as slow response time to mouse events or chopped dialog windows (Bug report [https://bugs.eclipse.org/bugs/show_bug.cgi?id=483545]). A possible workaround for this issue is to force Eclipse to run under XWayland.
  
With the superuser, open the file {{ic|/usr/bin/eclipse}} and append this line before the {{ic|exec}} line :
+
With the superuser, open the file {{ic|/usr/bin/eclipse}} and append this line before the {{ic|exec}} line:
 +
 
 
     export GDK_BACKEND=x11
 
     export GDK_BACKEND=x11
  

Latest revision as of 00:24, 14 January 2020

Eclipse it is an open source community project aimed at providing a universal development platform. The Eclipse project is best known for its multiplatform integrated development environment (IDE). Arch Linux packages (and this guide) are specifically related to the IDE.

Eclipse IDE is largely written in Java, but can be used to develop applications in many languages, including Java, C / C++, PHP, Perl, Rust and Python. The IDE can also provide subversion support and task management.

Installation

Install one of the following packages:

You cannot install several of them at the same time as they conflict, see FS#45577: choose the package above which meets your needs immediately and add support for the additional languages you need through #Plugins.

Plugins

Many plugins are easily installed using pacman (look Eclipse plugin package guidelines for more information). This will also keep them updated. Alternatively, you can choose the Eclipse Marketplace or the internal plugin manager.

Add the default update site

Be sure to verify that the default update site for your version of Eclipse is configured so that plug-in dependencies can be installed automatically. The most current version of Eclipse is Photon and the default update site is: http://download.eclipse.org/releases/photon. Go to Help > Install New Software > Add, fill in the name to easily identify the update site later - for example, Photon Software Repository - and fill in the location with the URL.

Eclipse Marketplace

Note: make sure you have followed the Add the default update site section.

To use the Eclipse Marketplace, install it first: go to Help > Install new software > Switch to the default update site > General Purpose Tools > Marketplace Client. Restart Eclipse and it will be available in Help > Eclipse Marketplace.

Plugin manager

Note: make sure you have followed the Add the default update site section.

Use 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.

Note:
  • 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/lib/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 would not be recognized any longer.
  • Do not use Eclipse as root for your everyday work.

Updates via 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 4.5 (Mars), check you have enabled this repository:

http://download.eclipse.org/releases/mars

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.

List of plugins

  • AVR — AVR microcontroller plugin.
http://avr-eclipse.sourceforge.net/wiki/index.php/The_AVR_Eclipse_Plugin || eclipse-avrAUR
  • Aptana — HTML5/CSS3/JavaScript/Ruby/Rails/PHP/Pydev/Django support. Also available as standalone application.
http://www.aptana.com/ || aptana-studioAUR
  • IvyDE — IvyDE dependency Manager.
https://ant.apache.org/ivy/ivyde/ || eclipse-ivydeAUR
  • Markdown — Markdown editor plugin for Eclipse.
http://www.winterwell.com/software/markdown-editor.php || eclipse-markdownAUR
http://pydev.org/ || eclipse-pydevAUR
https://github.com/subclipse/subclipse || eclipse-subclipseAUR
  • Subversive — Alternative Subversion support.
https://www.eclipse.org/subversive/ || eclipse-subversiveAUR
  • TestNG — TestNG support.
http://testng.org/doc/eclipse.html || eclipse-testngAUR
  • TeXlipseLaTeX support.
http://texlipse.sourceforge.net/ || eclipse-texlipseAUR
  • Checkstyle — Eclipse Checkstyle support.
http://eclipse-cs.sourceforge.net/ || eclipse-checkstyleAUR

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:

  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 /usr/lib/jvm/java-8-openjdka/jre/lib/rt.jar item under "JRE system libraries:", then click Javadoc Location....
  4. Enter "https://docs.oracle.com/javase/8/docs/api/" in the "Javadoc location path:" text field.

Offline version

You can store the documentation locally by installing the openjdk8-doc package. Eclipse may be able to find the javadocs automatically. If that does not work, set Javadoc location for rt.jar to file:/usr/share/doc/java8-openjdk/api.

Troubleshooting

Ctrl+X closes Eclipse

Part of this bug. Just look in ~/workspace/.metadata/.plugins/org.eclipse.e4.workbench/workbench.xmi and delete the wrong Ctrl+X combination. Usually it is the first one.

Dark theme

Eclipse supplies a Dark theme which can be enabled in Window > Preferences > General > Appearance and selecting the Dark theme.

The dark theme uses its own colours rather than the GTK theme colours, if you prefer it to fully respect GTK colour settings, then remove or move to backup sub folder all of the .css files from /usr/lib/eclipse/plugins/org.eclipse.ui.themes_version/css/, replacing the version with the appropriate version number.

Change Default Window Title Font Size

You cannot change the window title font size using the Eclipse preferences, you must edit the actual theme .css files. These are located under /usr/lib/eclipse/plugins/org.eclipse.themes_version/css/ directory, where version is the actual theme version number.

Use an text editor to edit the appropriate file, e.g. e4_default_gtk.css if you are using the "GTK theme".

In this file, search for .MPartStack, and change the font-size to your desired size:

.MPartStack {
       font-size: 9;
       swt-simple: false;
       swt-mru-visible: false;
}
Note: This needs to be redone whenever eclipse is upgraded.

Disable GTK 3

If the SWT GTK 3 UI gets buggy or unusable, it can be disabled by prepending SWT_GTK3=0 environment variable when starting Eclipse:

SWT_GTK3=0 eclipse

Another option to achieve the same effect is to add the following to Eclipse's ini file, before --launcher.appendVmargs:

/usr/lib/eclipse/eclipse.ini
--launcher.GTK_version
2

Freshplayerplugin

Eclipse is not compatible with freshplayerpluginAUR. See https://github.com/i-rinat/freshplayerplugin/issues/298.

Eclipse 4.6 may not open the marketplace properly

See this bug. You can take following two steps to fix it:

eclipse -consoleLog -application org.eclipse.equinox.p2.director -uninstallIU org.apache.httpcomponents.httpclient/4.3.6.v201411290715
cd /usr/lib/eclipse/ && sudo rm plugins/org.apache.httpcomponents.httpclient_4.3.6.v201411290715.jar

Show in System Explorer does not work

See this guide. Go to Window > Preferences > General > Workspace and change the command launching system explorer. As Xfce user you may like to change it to thunar ${selected_resource_uri} to open the selected folder with thunar.

Display issues under Wayland

When running Eclipse on Wayland, you may encounter rendering issues such as slow response time to mouse events or chopped dialog windows (Bug report [1]). A possible workaround for this issue is to force Eclipse to run under XWayland.

With the superuser, open the file /usr/bin/eclipse and append this line before the exec line:

   export GDK_BACKEND=x11

This will force the execution of Eclipse on XWayland.

See also