From Fedora Project Wiki

(We now ship eclipse photran)
 
 
(88 intermediate revisions by 10 users not shown)
Line 1: Line 1:
(shamelessly copied from DaveMalcolm's page at http://live.gnome.org/Eclipse)
+
[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.
  
= Eclipse =
+
It is shipped in Fedora (>= 4). Packaging guidelines for Eclipse plugins can be found here: [[Packaging/EclipsePlugins]].
  
== What is Eclipse? ==
+
== Installation ==
Eclipse is an awesome IDE for creating apps, in various languages.  It has a GTK+ UI that is much more accesible to regular programmers from a Windows environment than the tools traditionally used by FOSS hackers.
+
It can be installed via merely running:
  
It is currently best for developing apps in Java, but support for C, C++, C# and Python is rapidly catching up.
+
<pre>
 +
sudo dnf install eclipse
 +
</pre>
  
It was originally a (very) large body of code that IBM open-sourced. There is now a large community of companies and developers using and extending 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).  
  
It has its own Open Source license (the Eclipse Public Library, or EPL).
+
Would you like to help?
  
It is shipped in FedoraCore (>= 4).  Plug-ins will be added to Fedora as time permits or as people do the necessary work. ;)
+
Talk to us on IRC or the [https://admin.fedoraproject.org/mailman/listinfo/java-devel/ java-devel mailing list].  Package a plugin for Fedora!
  
== Fedora Eclipse ==
+
== Plugins We Ship ==
  
Fedora Eclipse is a community project encompassing everything Eclipse-related in Fedora. We ship the Eclipse SDK, CDT, as well as the PyDev, ChangeLog, and Bugzilla plugins. We are working on making plugin packagin easier, and also on packaging more plugins.
+
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.
  
Would you like to help?
+
<!-- Please keep these in alphabetical order -->
  
Visit our [http://sourceware.org/eclipse current website] . Talk to us on IRC or the fedora-devel-java mailing list. Package a plug-in for Fedora!
+
[https://www.eclipse.org/egit/ EGit] &mdash; support for working with Git repositories.
  
== Plug-ins We Ship ==
+
[https://www.eclipse.org/emf EMF] &mdash; Eclipse Modeling Framework.
  
[http://sourceware.org/eclipse/changelog ChangeLog]  
+
[https://www.eclipse.org/gef GEF] &mdash; Eclipse Graphical Editing Framework (''not'' the [http://www.eclipse.org/vep Visual Editor]).
  
[http://pydev.sf.net PyDev]
+
[https://eclipse.org/m2e/ M2E] &mdash; Maven integration for Eclipse.
  
[http://www.eclipse.org/mylar Mylar/Mylyn] -- a task-focused UI for Eclipse with bugzilla integration.  (Note:  Mylar was renamed to Mylyn for its version 2.0 and beyond but we are not yet shipping a renamed version.  This change in package names will happen for Fedora 8.)
+
[https://subclipse.tigris.org Subclipse] &mdash; support for working with Subversion repositories.
  
[http://www.eclipse.org/emf EMF] -- Eclipse Modelling Framework
+
[https://eclipse.org/webtools/ Webtools] &mdash; Eclipse WTP project (partially packaged).
  
[http://www.eclipse.org/gef GEF]  -- Eclipse Graphical Editing Framework (''not'' the [http://www.eclipse.org/vep Visual Editor] )
+
== Contact ==
  
[http://subclipse.tigris.org Subclipse] -- support for working with Subversion repositories
+
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.eclipse.org/photran Photran] -- Fortran support for Eclipse
+
[http://www.redhat.com/mailman/listinfo/fedora-devel-java-list/ Fedora Java Mailing list]
  
== Contact ==
+
[http://www.eclipse.org Eclipse (upstream)]
 +
 
 +
[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".
  
[http://sourceware.org/eclipse Fedora Eclipse Website]
+
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:
  
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.
+
<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.
  
[http://www.redhat.com/mailman/listinfo/fedora-devel-java-list/ Fedora Java Mailing list]
+
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.
  
[http://www.eclipse.org Eclipse (upstream)]
+
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
  
[http://planet.eclipse.org Planet Eclipse]
+
Create a file ~/.options and add the following flags to it:
  
[http://developer.classpath.org/mediation/ GNU Classpath Wiki]
+
<pre>
 +
org.eclipse.equinox.p2.core/debug=true
 +
org.eclipse.equinox.p2.core/reconciler=true
 +
org.eclipse.equinox.p2.garbagecollector/debug=true
 +
</pre>
  
[http://planet.classpath.org Planet Classpath]
+
Then run eclipse from a terminal with the following flags:
 +
<pre>eclipse -consolelog -debug -clean >& log</pre>
  
[http://gcc.gnu.org/java GCJ - GNU Compiler for Java]
+
Attached this log to the bug you file.
  
== Testing ==
+
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>
  
It has [https://www.redhat.com/archives/fedora-devel-java-list/2005-July/msg00088.html automated tests] .  You can also run [https://www.redhat.com/archives/fedora-devel-java-list/2005-April/msg00010.html individual plug-in tests] .
+
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:
  
== References ==
+
<pre>
 +
diff `find /usr/lib*/eclipse/ -name bundles.info` `find ~/.eclipse/ -name bundles.info` | grep "<" | sed s/"< "/""/ >> `find ~/.eclipse/ -name bundles.info`
 +
</pre>
  
* [http://www.redhat.com/magazine/018apr06/features/eclipse_foox/ Introduction to Eclipse on Fedora]
+
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.
* [http://www.redhat.com/magazine/018apr06/features/eclipse_tromey/ Confessions of an Eclipse convert]
+
Please file a bug which includes the diff.
* [http://www.gotmono.com/docs/ide/eclipse.html Eclipse for developing Mono applications]
 
  
 
----
 
----
 
[[Category:Documentation]]
 
[[Category:Documentation]]
 +
[[Category:Integrated development environments]]

Latest revision as of 08:00, 10 February 2021

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:

sudo dnf install 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).

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.

Fedora Java Mailing list

Eclipse (upstream)

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

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.