From Fedora Project Wiki

m (Minor typos)
(→‎Flathub: link)
 
(40 intermediate revisions by 6 users not shown)
Line 1: Line 1:
= Eclipse =
[https://www.eclipse.org/ide '''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? ==
== Installation ==
[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.
=== Eclipse ===
[https://www.eclipse.org/downloads/packages/ Eclipse Packages] offers their own installers and tarballs for different editions.


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.
=== Flathub ===
The Java IDE can also be installed as a Flatpak package from [https://flathub.org/apps/org.eclipse.Java Flathub]:


It has its own Open Source license (the Eclipse Public Library, or EPL).
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]].
== Fedora Eclipse ==
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] and [http://fedorahosted.org/eclipse-fedorapackager Fedora Packager for Eclipse]).
Would you like to help?
Talk to us on IRC or the [https://admin.fedoraproject.org/mailman/listinfo/java-devel/ java-devel mailing list].  Package a plug-in for Fedora!
== Plug-ins We Ship ==
<!-- Please keep these in alphabetical order -->
[http://www.eclipse.org/linuxtools/projectPages/autotools Autotools] (part of CDT SRPM)
[http://www.eclipse.org/birt BIRT]
[http://cmakeed.sourceforge.net/ CMakeed] -- Editor for CMake files
[http://www.eclipse.org/cdt CDT] -- C/C++ Development Tooling
[http://www.eclipse.org/linuxtools/projectPages/changelog/ ChangeLog]
[http://desktop-eclipse.open.collab.net/servlets/ProjectProcess?pageID=MEuUjb&freeformpage=Merge%20Client CollabNet Merge Client for Subclipse] -- Take advantage of the new merge cleverness in Subversion 1.5+
[http://eclipse.org/dltk Dynamic Language Toolkit] -- Complete with TCL and Ruby IDEs
[http://www.eclipse.org/datatools DTP] -- Database Development Tools
[http://www.eclemma.org/ EclEmma] -- Code coverage tool to help you enhance your unit tests.
[http://git.or.cz/gitwiki/EclipsePlugin EGit] -- Support for working with Git repositories
[http://www.eclipse.org/emf EMF]  -- Eclipse Modeling Framework
[http://www.epic-ide.org/ EPIC] -- Perl tooling
[http://www.eclipse.org/gef GEF]  -- Eclipse Graphical Editing Framework (''not'' the [http://www.eclipse.org/vep Visual Editor] )
[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. See also [[Eclipse/MylynRedHatBugzillaSetupGuide | Eclipse Mylyn Red Hat Bugzilla setup instructions]] and [[Eclipse/MylynPackaging | Eclipse Mylyn packaging guide]] for more Mylyn related information.
[http://www.eclipse.org/linuxtools/projectPages/oprofile OProfile]
[http://www.eclipse.org/ptp Parallel Tools Platform (PTP)] -- Parallel and Fortran programming support for Eclipse
[http://www.phpeclipse.com/ PHPEclipse] -- PHP Development Tooling
[http://pydev.sf.net PyDev] -- Python IDE for Eclipse
[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
[http://stapgui.sourceforge.net/ SystemTap GUI]
[http://www.eclipse.org/linuxtools/projectPages/valgrind Valgrind]
== Plug-ins We'd Like To Ship ==
* WTP
** needs some non-Eclipse deps, all of which may not be in Fedora
** tracker bug:  [https://bugzilla.redhat.com/486369 486369]
** old SRPM and .spec uploaded here (most likely won't build, needs work):
*** http://overholt.fedorapeople.org/eclipse-webtools.spec
*** http://overholt.fedorapeople.org/eclipse-webtools-1.5.0-2.fc10.src.rpm
* [http://eclipse.org/vep VE]
** requested [https://bugzilla.redhat.com/show_bug.cgi?id=473779 here]
** development has been [http://dev.eclipse.org/blogs/yvesyang/2009/06/26/eclipse-ve-gets-revived/ re-started upstream]
* [http://wiki.eclipse.org/index.php/Mylyn_Extensions#Atlassian_JIRA_.28Mylyn_Project.29 Mylyn's JIRA plugin]
** [https://bugzilla.redhat.com/show_bug.cgi?id=251747 bug to ship JIRA plugin]
** needs axis 1.4 with OSGi metadata ([https://bugzilla.redhat.com/show_bug.cgi?id=497126 bug #497126])
*** <s>needs org.apache.commons.discovery_0.2.0 (hopefully 0.4 we have is acceptable) ([https://bugzilla.redhat.com/show_bug.cgi?id=497128 bug to add OSGi metadata])</s>
*** <s>needs javax.wsdl_1.5.1 ([https://bugzilla.redhat.com/show_bug.cgi?id=497130 bug to add OSGi metadata])</s>
*** needs javax.xml.soap_1.2.0 ([https://bugzilla.redhat.com/show_bug.cgi?id=497139 bug to add OSGi metadata])
*** javax.xml.rpc_1.1.0 ([https://bugzilla.redhat.com/show_bug.cgi?id=497141 bug to add OSGi metadata])
== Plug-ins Which Need Packaging Work ==
* BIRT
** all of it needs  WTP
** Tracker bug to get WTP built (filed against BIRT since that's what needs it) [https://bugzilla.redhat.com/486369 486369]
== 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.
[http://www.redhat.com/mailman/listinfo/fedora-devel-java-list/ Fedora Java Mailing list]
[http://www.eclipse.org Eclipse (upstream)]
[http://planet.eclipse.org Planet Eclipse]
[http://developer.classpath.org/mediation/ GNU Classpath Wiki]
[http://planet.classpath.org Planet Classpath]
[http://gcc.gnu.org/java GCJ - GNU Compiler for Java]
== Testing ==
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] .
Running the Eclipse SDK automated tests against the installed RPMs can be done using the following steps:
# <tt>$ svn co http://dev.eclipse.org/svnroot/technology/org.eclipse.linuxtools/sdktests/3.4.1/Fedora eclipse-sdk-tests</tt>
# <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
We appreciate any and all reports of success or failure with the SDK tests.  The fedora-devel-java-list mailing list is a fine place to send them.
== 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-rcp eclipse-platform
</pre>
Make sure that there is no output when you run the above command. Next, run:
<pre>
<pre>
rpm -qf /usr/lib*/eclipse/p2/org.eclipse.equinox.p2.engine/profileRegistry/PlatformProfile.profile/*.profile.gz
flatpak install org.eclipse.Java
</pre>
</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
You may also install it using Gnome Software or KDE Discover; look for ''Eclipse IDE for Java Developers''.
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
== Troubleshooting ==
a bug here:  https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&component=eclipse
See [https://github.com/flathub/org.eclipse.Java Eclipse on Flathub] for bug reports and pull requests on the Flatpak manifest.


Create a file ~/.options and add the following flags to it:
=== No Splashscreen Image ===
As the splash is stored as legacy BMP try
<pre>yum install gdk-pixbuf2-modules-extra</pre>
to fix it.


<pre>
== Contact ==
org.eclipse.equinox.p2.core/debug=true
Most of the Fedora "free java" people hang out on [ircs://irc.libera.chat#fedora-java #fedora-java] on [http://libera.chat Libera]. The [https://www.eclipse.org/linuxtools/ Eclipse Linux Tools] upstream project is also responsible for packaging across distributions.
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.
 
== Plans ==
We ship the Eclipse SDK (<tt>eclipse</tt> SRPM) version 3.6.1 in Fedora 14.  Other [http://www.eclipse.org/helios/ Helios] release train projects are also updated to their Helios versions.
 
The other plugins we ship '''should''' work with Eclipse 3.6 without problems.  We will of course have to coordinate testing them all.
 
=== Fedora Eclipse Branding ===
 
Up to and including Fedora 11, we shipped a branding plugin with a custom splash screen and product ID.  From Fedora 12 onwards, we will no longer be doing this.
 
==== Updating the branding for a new version ====
 
''This section is no longer important but is kept for historical purposes.''  The splash screen itself was originally done by Diana Fong and given to us as a PSD file.  It is kept with the rest of the branding plugin in CVS:
 
<tt>:pserver:anonymous@sources.redhat.com:/cvs/eclipse</tt>
 
<tt>branding/org.fedoraproject.ide.platform</tt>
 
People wishing to commit will have to have a Sourceware account.  We should probably move this to Fedora Hosted. In the meantime, use this form to request an account (project:  eclipse, sponsor:  Andrew Overholt):
 
http://sourceware.org/cgi-bin/pdw/ps_form.cgi
 
When updating the branding to a new version, you will need to:
 
* update the product file <tt>fedoraeclipse.product</tt> to include the build ID matching upstream's release build (ex. <tt>http://download.eclipse.org/eclipse/downloads/drops/R-3.4.2-200902111700</tt> gives a build ID of 20090211-1700)
* be sure to hit the synchronize link on the "Overview" page of the product editor to sync up the various generated files
* make a new <tt>splash.bmp</tt> (yes, it is an actual BMP):
** open the <tt>.psd</tt> file in the Gimp
** adjust the visible layers of the numbering in the Gimp to have the correct version shown
*** for versions that are not present in the PSD, you will need to use the Gimp to draw a number that looks very close to the font originally used
** export the visible layers you want to <tt>splash.bmp</tt>; do '''not''' include the Fedora logo layer in the resulting <tt>splash.bmp</tt>
** refresh the <tt>splash.bmp</tt> file in your workspace and open it to ensure it is what you want
* commit your changes.  Comparing two previous tags (ex. <tt>fedoraeclipse-3_4_1</tt> vs. <tt>fedoraeclipse-3_4_2</tt>) is a helpful indicator to guarantee you've made all of the necessary changes.
** do '''not''' include the PSD file in build.properties; it should not be shipped in the SRPM/RPM
* branch and tag for the new version; follow previous tags and branch names to be consistent
* update <tt>eclipse.spec</tt> to reflect the new locations and generate a new <tt>org.fedoraproject.ide.platform-%{version}.zip</tt>
 
== References ==


* [http://www.redhat.com/magazine/018apr06/features/eclipse_foox/ Introduction to Eclipse on Fedora]  
* [https://lists.fedoraproject.org/archives/list/java-devel@lists.fedoraproject.org/ Fedora Java Mailing list]  
* [http://www.redhat.com/magazine/018apr06/features/eclipse_tromey/ Confessions of an Eclipse convert]  
* [https://www.eclipse.org Eclipse foundation] (upstream)
* [http://www.gotmono.com/docs/ide/eclipse.html Eclipse for developing Mono applications]  
* [https://chat.eclipse.org/ Eclipse Foundation Chat Community] (Matrix based)
* [https://planet.eclipse.org Planet Eclipse] (Blogs)


----
----
[[Category:Documentation]]
[[Category:Documentation]]
[[Category:Integrated development environments]]

Latest revision as of 11:21, 6 December 2024

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.

Installation

Eclipse

Eclipse Packages offers their own installers and tarballs for different editions.

Flathub

The Java IDE can also be installed as a Flatpak package from Flathub: 

flatpak install org.eclipse.Java

You may also install it using Gnome Software or KDE Discover; look for Eclipse IDE for Java Developers.

Troubleshooting

See Eclipse on Flathub for bug reports and pull requests on the Flatpak manifest.

No Splashscreen Image

As the splash is stored as legacy BMP try 

yum install gdk-pixbuf2-modules-extra

to fix it.

Contact

Most of the Fedora "free java" people hang out on #fedora-java on Libera. The Eclipse Linux Tools upstream project is also responsible for packaging across distributions.

Retrieved from "https://fedoraproject.org/w/index.php?title=Eclipse&oldid=726848"