From Fedora Project Wiki

(Change rpm instructions to flatkpak; rpms are deprecated for this package)
 
(63 intermediate revisions by 11 users not shown)
Line 1: Line 1:
= 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.


== What is Eclipse? ==
It is shipped in Fedora (>= 4). Packaging guidelines for Eclipse plugins can be found here: [[Packaging/EclipsePlugins]].
[http://www.eclipse.org Eclipse] is an awesome IDE with tooling for 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 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.
== Installation ==
It can be installed via merely running:


It has its own Open Source license (the Eclipse Public Library, or EPL).
<pre>
flatpak install org.eclipse.Java
</pre>


It is shipped in Fedora (>= 4).  Plug-ins are continuously being added to Fedora.  We aim to take care of Eclipse plugin review requests quickly.  Packaging guidelines for Eclipse plugins can be found here:  [[Packaging/EclipsePlugins]].
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 many plugins (see below).  We are working on making plugin packaging easier (see [http://www.eclipse.org/linuxtools/projectPages/rpmstubby RPM Stubby].


Would you like to help?
Would you like to help?


Talk to us on IRC or the [https://www.redhat.com/archives/fedora-devel-java-list/ fedora-devel-java mailing list].  Package a plug-in for Fedora!
Talk to us on IRC or the [https://admin.fedoraproject.org/mailman/listinfo/java-devel/ java-devel mailing list].  Package a plugin for Fedora!
 
== Plug-ins We Ship ==
<!-- Please keep these in alphabetical order -->


[http://www.eclipse.org/linuxtools/projectPages/autotools Autotools] (part of CDT SRPM)
== Plugins We Ship ==


[http://cmakeed.sourceforge.net/ CMakeed] -- Editor for CMake files
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.


[http://www.eclipse.org/cdt CDT]
<!-- Please keep these in alphabetical order -->


[http://www.eclipse.org/linuxtools/projectPages/changelog/ ChangeLog]  
[https://www.eclipse.org/egit/ EGit] &mdash; support for working with Git repositories.


[http://www.eclemma.org/ EclEmma] -- Code coverage tool to help you enhance your unit tests.
[https://www.eclipse.org/emf EMF] &mdash; Eclipse Modeling Framework.


[http://git.or.cz/gitwiki/EclipsePlugin EGit] -- git support
[https://www.eclipse.org/gef GEF] &mdash; Eclipse Graphical Editing Framework (''not'' the [http://www.eclipse.org/vep Visual Editor]).


[http://www.eclipse.org/emf EMF] -- Eclipse Modeling Framework
[https://eclipse.org/m2e/ M2E] &mdash; Maven integration for Eclipse.


[http://www.epic-ide.org/ EPIC] -- Perl tooling
[https://subclipse.tigris.org Subclipse] &mdash; support for working with Subversion repositories.


[http://www.eclipse.org/gef GEF]  -- Eclipse Graphical Editing Framework (''not'' the [http://www.eclipse.org/vep Visual Editor] )
[https://eclipse.org/webtools/ Webtools] &mdash; Eclipse WTP project (partially packaged).
 
[http://moreunit.sourceforge.net/ MoreUnit] -- Helper for writing more and better unit tests.
 
[http://www.eclipse.org/mylyn Mylyn]  -- a task-focused UI for Eclipse with bugzilla and trac integration.
 
[http://www.eclipse.org/photran Photran] -- Fortran support for Eclipse
 
[http://www.phpeclipse.com/ PHPEclipse] -- PHP tooling
 
[http://pydev.sf.net PyDev]
 
[http://bastian-bergerhoff.com/eclipse/features/web/QuickREx/toc.html QuickREx] -- Regular expression tester
 
[http://www.eclipse.org/linuxtools/projectPages/specfile/ RPM Specfile Editor]
 
[http://www.eclipse.org/linuxtools/projectPages/rpmstubby/ RPM Specfile Generator] -- This plugin makes packaging other plugins really easy.
 
[http://oss.tresys.com/projects/setools Eclipse SETools] -- SELinux policy analysis tools
 
[http://sourceforge.net/projects/shelled Shelled] -- Editor for shell scripts
 
[http://oss.tresys.com/projects/slide SLIDE] -- SLIDE is an integrated development environment (IDE) for Security Enhanced Linux (SELinux) developers and integrators
 
[http://subclipse.tigris.org Subclipse]  -- support for working with Subversion repositories
 
 
Coming soon in rawhide:
 
[http://www.eclipse.org/birt BIRT] [https://bugzilla.redhat.com/show_bug.cgi?id=485424 review request]
 
[http://www.eclipse.org/datatools DTP] <s>[https://bugzilla.redhat.com/show_bug.cgi?id=484676 review request]</s>
 
[http://www.eclipse.org/linuxtools/projectPages/oprofile OProfile]
 
[http://stapgui.sourceforge.net/ SystemTap GUI] [https://bugzilla.redhat.com/show_bug.cgi?id=483205 review request]
 
[http://www.eclipse.org/linuxtools/projectPages/valgrind Valgrind]
 
== Plug-ins We'd Like To Ship ==
* BIRT
** all of it needs DTP and WTP
** could ship a stripped-down version in the meantime
* DTP
** Package of [http://sourceforge.net/projects/lpg/ lpgjavaruntime]
** Fix build with lucene 2 and submit it upstream
** <s>Fix build with java 6 - Fixed in latest build in rawhide.
** <s>review request:  https://bugzilla.redhat.com/show_bug.cgi?id=484676</s> package built with just a few features
** tracker bug to get all dependencies in:  [https://bugzilla.redhat.com/show_bug.cgi?id=485460 https://bugzilla.redhat.com/show_bug.cgi?id=485460]
* WTP
** probably needs some non-Eclipse deps
* Valgrind
** needs BIRT
** see [[Features/EclipseProfilingTools]]
* OProfile
** could go in now
** see [[Features/EclipseProfilingTools]]
* [http://eclipse.org/vep VE]
** requested [https://bugzilla.redhat.com/show_bug.cgi?id=473779 here]
** what's the status of VE and recent Eclipse SDKs?


== Contact ==
== Contact ==
<!-- [http://sourceware.org/eclipse Fedora Eclipse Website] -->


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.
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.
Line 108: Line 45:
[http://www.eclipse.org Eclipse (upstream)]  
[http://www.eclipse.org Eclipse (upstream)]  


[http://planet.eclipse.org Planet Eclipse]  
[http://planet.eclipse.org Planet Eclipse]


[http://developer.classpath.org/mediation/ GNU Classpath Wiki]
== Troubleshooting Eclipse in Fedora ==


[http://planet.classpath.org Planet Classpath]
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://gcc.gnu.org/java GCJ - GNU Compiler for Java]
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:


== Testing ==
<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.


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


Running the Eclipse SDK automated tests against the installed RPMs can be done using the following steps:
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


# <tt>$ svn co http://dev.eclipse.org/svnroot/technology/org.eclipse.linuxtools/sdktests/3.4.1/Fedora eclipse-sdk-tests</tt>
Create a file ~/.options and add the following flags to it:
# <tt>$ cd eclipse-sdk-tests</tt>
# <tt>$ ./build.sh</tt>
# (... wait for build)
# <tt># rpm -Uvh RPMS/{x86_64,i386,etc.}/eclipse-tests-3.4*.rpm</tt>
# <tt>$ cd <somewhere you can write></tt>
# <tt>$ /usr/lib (or lib64) /eclipse/dropins/eclipse/runtests</tt>
# (... wait for tests to run)</tt>
# <tt>$ ls /tmp/eclipseSDKtests/results/html</tt>
# View results in browser: file:///tmp/eclipseSDKtests/results/html


== Plans ==
<pre>
According to [[Releases/11/Schedule]], Fedora 11 is currently scheduled to be released on 2009-05-26. This is before the schedule release of Eclipse 3.5 which will be some time after 2009-06-12, according to [http://www.eclipse.org/projects/project-plan.php?projectid=eclipse#release_milestones http://www.eclipse.org/projects/project-plan.php?projectid=eclipse#release_milestones]. We would like to avoid having 5 months of a gap between the release of Eclipse 3.5 and it being available in a Fedora release. As such, we plan on doing an upgrade to 3.5 some time in the Fedora 11 life cycle.  See this tracker bug for getting Eclipse 3.5 ready:
org.eclipse.equinox.p2.core/debug=true
org.eclipse.equinox.p2.core/reconciler=true
org.eclipse.equinox.p2.garbagecollector/debug=true
</pre>


There are also the following tracker bugs for various packages we ship and for upgrading them to their [http://wiki.eclipse.org/Galileo Galileo] version:
Then run eclipse from a terminal with the following flags:
<pre>eclipse -consolelog -debug -clean >& log</pre>


* [https://bugzilla.redhat.com/show_bug.cgi?id=485488 Autotools] (included under CDT umbrella)
Attached this log to the bug you file.
* BIRT (not in yet so no bugzilla component)
* [https://bugzilla.redhat.com/show_bug.cgi?id=485488 CDT]
* [https://bugzilla.redhat.com/show_bug.cgi?id=485492 DTP]
* [https://bugzilla.redhat.com/show_bug.cgi?id=485490 EMF]
* [https://bugzilla.redhat.com/show_bug.cgi?id=485493 GEF]
* [https://bugzilla.redhat.com/show_bug.cgi?id=485494 Mylyn]


The other plugins we ship '''should''' work with Eclipse 3.5 without problems. We will of course have to coordinate testing them all.
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>


In order to coordinate this effort, we will be requesting a koji tag (and repo?) to use for our builds and so that others can easily consume this work and report errors.
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 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.

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.