(Change rpm instructions to flatkpak; rpms are deprecated for this package) |
|||
| (67 intermediate revisions by 11 users not shown) | |||
| Line 1: | Line 1: | ||
[http://www.eclipse.org '''Eclipse'''] is an open-source (under the Eclipse Public License, or EPL) powerful [[Integrated development environment|IDE]] with tooling for various languages. It has a GTK+ user interface and is written in Java. As it is written in Java it is cross-platform and capable of running on Linux, MacOS and Windows. It is maintained and used by a large community of volunteers and companies. | |||
= | It is shipped in Fedora (>= 4). Packaging guidelines for Eclipse plugins can be found here: [[Packaging/EclipsePlugins]]. | ||
[ | |||
It | == Installation == | ||
It can be installed via merely running: | |||
<pre> | |||
flatpak install org.eclipse.Java | |||
</pre> | |||
You may also install it using Gnome Software or KDE Discover; look for Eclipse IDE for Java Developers. | |||
== Fedora Eclipse == | == Fedora Eclipse == | ||
Fedora Eclipse is a community project encompassing everything Eclipse-related in Fedora. We ship the Eclipse SDK along with some plugins (see below). | |||
Fedora Eclipse is a community project encompassing everything Eclipse-related in Fedora. We ship the Eclipse SDK along with | |||
Would you like to help? | Would you like to help? | ||
Talk to us on IRC or the [https:// | Talk to us on IRC or the [https://admin.fedoraproject.org/mailman/listinfo/java-devel/ java-devel mailing list]. Package a plugin for Fedora! | ||
== | == Plugins We Ship == | ||
It is highly recommended that Eclipse plugins are installed via Eclipse Marketplace or the plugin specific update site but there are some plugins that are shipped in RPM format too. | |||
<!-- Please keep these in alphabetical order --> | |||
[ | [https://www.eclipse.org/egit/ EGit] — support for working with Git repositories. | ||
[ | [https://www.eclipse.org/emf EMF] — Eclipse Modeling Framework. | ||
[http://www. | [https://www.eclipse.org/gef GEF] — Eclipse Graphical Editing Framework (''not'' the [http://www.eclipse.org/vep Visual Editor]). | ||
[ | [https://eclipse.org/m2e/ M2E] — Maven integration for Eclipse. | ||
[ | [https://subclipse.tigris.org Subclipse] — support for working with Subversion repositories. | ||
[ | [https://eclipse.org/webtools/ Webtools] — Eclipse WTP project (partially packaged). | ||
== Contact == | |||
[http:// | Most of the Fedora "free java" people hang out on #fedora-java on [http://freenode.net Freenode] . There are also people on #classpath also on Freenode. Community around the [http://www.eclipse.org/linuxtools/ Eclipse Linux Tools] project is emerging now and developers are hanging out on #eclipse-linux on Freenode. | ||
[http://www. | [http://www.redhat.com/mailman/listinfo/fedora-devel-java-list/ Fedora Java Mailing list] | ||
[http://www.eclipse.org | [http://www.eclipse.org Eclipse (upstream)] | ||
[http:// | [http://planet.eclipse.org Planet Eclipse] | ||
== Troubleshooting Eclipse in Fedora == | |||
The way Eclipse and its plugins are installed in Fedora differs from the way this is done upstream. This can | |||
sometimes lead to installation problems in Fedora. We are working on a solution to make installations | |||
more robust in future Fedora releases. In the meantime however, this section is meant to help you troubleshoot those problems. | |||
The main theme is "I updated eclipse and my plugins no longer show up". | |||
1. The first thing you want to do is to make sure that you have a bundles.info file in your ~/.eclipse directory | |||
<pre>find ~/.eclipse -name bundles.info</pre> | |||
If you find one then you can move on to step 2. If you don't find a file that means that there is a problem occurring | |||
early on during the startup of Eclipse. To start with you need to make sure that you have a standard Eclipse installation. To | |||
do so run the following: | |||
<pre> | |||
rpm -qV eclipse-platform | |||
</pre> | |||
Make sure that there is no output when you run the above command. Next, run: | |||
<pre> | |||
rpm -qf /usr/lib*/eclipse/p2/org.eclipse.equinox.p2.engine/profileRegistry/PlatformProfile.profile/*.profile.gz | |||
</pre> | |||
Make sure that there are no files which are not owned by any RPMs. | |||
If the result of the above commands is not clean that means that you don't have a clean Eclipse installation. It is possible that you may have | |||
run eclipse as root at some point. You can clean that up by removing all files which are not owned by any RPMs, and | |||
removing and reinstalling the eclipse RPMs. | |||
If both of the above outputs are clean, you will need to file a bug. Collect the following information and file | |||
a bug here: https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&component=eclipse | |||
Create a file ~/.options and add the following flags to it: | |||
== | <pre> | ||
org.eclipse.equinox.p2.core/debug=true | |||
org.eclipse.equinox.p2.core/reconciler=true | |||
org.eclipse.equinox.p2.garbagecollector/debug=true | |||
</pre> | |||
Then run eclipse from a terminal with the following flags: | |||
<pre>eclipse -consolelog -debug -clean >& log</pre> | |||
Attached this log to the bug you file. | |||
2. If you have found a bundles.info you will need to do is do a diff between your system bundles.info and user bundles.info: | |||
<pre>diff `find /usr/lib*/eclipse -name bundles.info` `find ~/.eclipse -name bundles.info`</pre> | |||
If there are any bundles present in the system bundles.info and not in the user bundles.info, these bundles are the source of the problem. If the bundles are installed and have the correct versions (the path to the bundles in stated relative to /usr/lib/eclipse or /usr/lib64/eclipse) then that means that things have been upgraded in a way that contradicts the previous installation. Adding those bundles to your user bundles.info will solve the problem. Before doing so backup your ~/.eclipse directory just in case. Here is a script wich will do that: | |||
<pre> | |||
diff `find /usr/lib*/eclipse/ -name bundles.info` `find ~/.eclipse/ -name bundles.info` | grep "<" | sed s/"< "/""/ >> `find ~/.eclipse/ -name bundles.info` | |||
</pre> | |||
If the extra bundles are not present or have different versions than what is in the system bundles.info, that means that the bundles.info is faulty and needs to be updated. | |||
Please file a bug which includes the diff. | |||
---- | ---- | ||
[[Category:Documentation]] | [[Category:Documentation]] | ||
[[Category:Integrated development environments]] | |||
Latest revision as of 14:28, 25 December 2022
Eclipse is an open-source (under the Eclipse Public License, or EPL) powerful IDE with tooling for various languages. It has a GTK+ user interface and is written in Java. As it is written in Java it is cross-platform and capable of running on Linux, MacOS and Windows. It is maintained and used by a large community of volunteers and companies.
It is shipped in Fedora (>= 4). Packaging guidelines for Eclipse plugins can be found here: Packaging/EclipsePlugins.
Installation
It can be installed via merely running:
flatpak install org.eclipse.Java
You may also install it using Gnome Software or KDE Discover; look for Eclipse IDE for Java Developers.
Fedora Eclipse
Fedora Eclipse is a community project encompassing everything Eclipse-related in Fedora. We ship the Eclipse SDK along with some plugins (see below).
Would you like to help?
Talk to us on IRC or the java-devel mailing list. Package a plugin for Fedora!
Plugins We Ship
It is highly recommended that Eclipse plugins are installed via Eclipse Marketplace or the plugin specific update site but there are some plugins that are shipped in RPM format too.
EGit — support for working with Git repositories.
EMF — Eclipse Modeling Framework.
GEF — Eclipse Graphical Editing Framework (not the Visual Editor).
M2E — Maven integration for Eclipse.
Subclipse — support for working with Subversion repositories.
Webtools — Eclipse WTP project (partially packaged).
Contact
Most of the Fedora "free java" people hang out on #fedora-java on Freenode . There are also people on #classpath also on Freenode. Community around the Eclipse Linux Tools project is emerging now and developers are hanging out on #eclipse-linux on Freenode.
Troubleshooting Eclipse in Fedora
The way Eclipse and its plugins are installed in Fedora differs from the way this is done upstream. This can sometimes lead to installation problems in Fedora. We are working on a solution to make installations more robust in future Fedora releases. In the meantime however, this section is meant to help you troubleshoot those problems. The main theme is "I updated eclipse and my plugins no longer show up".
1. The first thing you want to do is to make sure that you have a bundles.info file in your ~/.eclipse directory
find ~/.eclipse -name bundles.info
If you find one then you can move on to step 2. If you don't find a file that means that there is a problem occurring early on during the startup of Eclipse. To start with you need to make sure that you have a standard Eclipse installation. To do so run the following:
rpm -qV eclipse-platform
Make sure that there is no output when you run the above command. Next, run:
rpm -qf /usr/lib*/eclipse/p2/org.eclipse.equinox.p2.engine/profileRegistry/PlatformProfile.profile/*.profile.gz
Make sure that there are no files which are not owned by any RPMs.
If the result of the above commands is not clean that means that you don't have a clean Eclipse installation. It is possible that you may have run eclipse as root at some point. You can clean that up by removing all files which are not owned by any RPMs, and removing and reinstalling the eclipse RPMs.
If both of the above outputs are clean, you will need to file a bug. Collect the following information and file a bug here: https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&component=eclipse
Create a file ~/.options and add the following flags to it:
org.eclipse.equinox.p2.core/debug=true org.eclipse.equinox.p2.core/reconciler=true org.eclipse.equinox.p2.garbagecollector/debug=true
Then run eclipse from a terminal with the following flags:
eclipse -consolelog -debug -clean >& log
Attached this log to the bug you file.
2. If you have found a bundles.info you will need to do is do a diff between your system bundles.info and user bundles.info:
diff `find /usr/lib*/eclipse -name bundles.info` `find ~/.eclipse -name bundles.info`
If there are any bundles present in the system bundles.info and not in the user bundles.info, these bundles are the source of the problem. If the bundles are installed and have the correct versions (the path to the bundles in stated relative to /usr/lib/eclipse or /usr/lib64/eclipse) then that means that things have been upgraded in a way that contradicts the previous installation. Adding those bundles to your user bundles.info will solve the problem. Before doing so backup your ~/.eclipse directory just in case. Here is a script wich will do that:
diff `find /usr/lib*/eclipse/ -name bundles.info` `find ~/.eclipse/ -name bundles.info` | grep "<" | sed s/"< "/""/ >> `find ~/.eclipse/ -name bundles.info`
If the extra bundles are not present or have different versions than what is in the system bundles.info, that means that the bundles.info is faulty and needs to be updated. Please file a bug which includes the diff.