From Fedora Project Wiki

m (Added DLTK to list of packaged plugins. Added link to the LPG package review.)
m (Cross off completed Galileo work.)
Line 151: Line 151:
* [ Autotools] (included under CDT umbrella)
* [ Autotools] (included under CDT umbrella)
* [ BIRT]
* <del>[ BIRT]</del>
* [ CDT]
* [ CDT]
* [ DTP]
* <del>[ DTP]</del>
* [ EMF]
* <del>[ EMF]</del>
* [ GEF]
* <del>[ GEF]</del>
* [ Mylyn]
* [ Mylyn]

Revision as of 20:18, 2 July 2009


What is Eclipse?

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.

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

Would you like to help?

Talk to us on IRC or the fedora-devel-java mailing list. Package a plug-in for Fedora!

Plug-ins We Ship

Autotools (part of CDT SRPM)


CMakeed -- Editor for CMake files



Dynamic Language Toolkit -- Complete with TCL and Ruby IDEs


EclEmma -- Code coverage tool to help you enhance your unit tests.

EGit -- git support

EMF -- Eclipse Modeling Framework

EPIC -- Perl tooling

GEF -- Eclipse Graphical Editing Framework (not the Visual Editor )

MoreUnit -- Helper for writing more and better unit tests.

Mylyn -- a task-focused UI for Eclipse with bugzilla and trac integration.


Photran -- Fortran support for Eclipse

PHPEclipse -- PHP tooling


QuickREx -- Regular expression tester

RPM Specfile Editor

RPM Specfile Generator -- This plugin makes packaging other plugins really easy.

Eclipse SETools -- SELinux policy analysis tools

Shelled -- Editor for shell scripts

SLIDE -- SLIDE is an integrated development environment (IDE) for Security Enhanced Linux (SELinux) developers and integrators

Subclipse -- support for working with Subversion repositories

SystemTap GUI


Plug-ins We'd Like To Ship

Plug-ins Which Need Packaging Work


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

GNU Classpath Wiki

Planet Classpath

GCJ - GNU Compiler for Java


It has automated tests . You can also run individual plug-in tests .

Running the Eclipse SDK automated tests against the installed RPMs can be done using the following steps:

  1. $ svn co eclipse-sdk-tests
  2. $ cd eclipse-sdk-tests
  3. $ ./
  4. (... wait for build)
  5. # rpm -Uvh RPMS/{x86_64,i386,etc.}/eclipse-tests-3.4*.rpm
  6. $ cd <somewhere you can write>
  7. $ /usr/lib (or lib64) /eclipse/dropins/eclipse/runtests
  8. (... wait for tests to run)
  9. $ ls /tmp/eclipseSDKtests/results/html
  10. 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.


We plan to ship the Eclipse SDK (eclipse SRPM) version 3.4.2 in Fedora 11. Other Ganymede release train projects should be updated to their Ganymede "Service Release 2" releases when they are available. We are using the following tracker bug for updating to 3.4.2:

Fedora 11 froze before the release of Eclipse 3.5 (Galileo). 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 hope to do an upgrade to 3.5 some time in the Fedora 11 life cycle. Status as of 2009-06-26 is that eclipse-build project upstream is coming along and we will move our builds to it once it is able to bootstrap itself.

There are also the following tracker bugs for various packages we ship and for upgrading them to their Galileo version:

The other plugins we ship should work with Eclipse 3.5 without problems. We will of course have to coordinate testing them all.

In order to coordinate this effort, we may be requesting a koji tag (and repo?) to use for our builds and so that others can easily consume this work and report errors.

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:


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):

When updating the branding to a new version, you will need to:

  • update the product file fedoraeclipse.product to include the build ID matching upstream's release build (ex. 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 splash.bmp (yes, it is an actual BMP):
    • open the .psd 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 splash.bmp; do not include the Fedora logo layer in the resulting splash.bmp
    • refresh the splash.bmp file in your workspace and open it to ensure it is what you want
  • commit your changes. Comparing two previous tags (ex. fedoraeclipse-3_4_1 vs. fedoraeclipse-3_4_2) is a helpful indicator to guarantee you've made all of the necessary changes.
    • do not include the PSD file in; 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 eclipse.spec to reflect the new locations and generate a new org.fedoraproject.ide.platform-%{version}.zip