From Fedora Project Wiki

(41 intermediate revisions by 10 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 NT. It is maintained and used by a large community of volunteers and companies.


== What is Eclipse? ==
It is shipped in Fedora (>= 4). Plugins are continuously being added to Fedora. The Fedora packaging team aims to take care of Eclipse plugin review requests quickly. 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>
sudo dnf install eclipse
</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]].
If you run into an error with glassfish-el you might be seeing [https://bugzilla.redhat.com/show_bug.cgi?id=1759176 bug 1759176] and you'll need to enable the Eclipse module first, then install eclipse.
 
<pre>
sudo dnf module enable eclipse:latest
sudo dnf install eclipse
</pre>


== Fedora Eclipse ==
== 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]).
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 ==
== Plugins We Ship ==
<!-- Please keep these in alphabetical order -->
<!-- Please keep these in alphabetical order -->


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


[http://cmakeed.sourceforge.net/ CMakeed] -- Editor for CMake files
[http://www.eclipse.org/birt BIRT]


[http://www.eclipse.org/cdt CDT]  
[http://cmakeed.sourceforge.net/ CMakeed] &mdash; editor for CMake files
 
[http://www.eclipse.org/cdt CDT] &mdash; C/C++ Development Tooling.


[http://www.eclipse.org/linuxtools/projectPages/changelog/ ChangeLog]  
[http://www.eclipse.org/linuxtools/projectPages/changelog/ ChangeLog]  


[http://www.eclemma.org/ EclEmma] -- Code coverage tool to help you enhance your unit tests.
[http://desktop-eclipse.open.collab.net/servlets/ProjectProcess?pageID=MEuUjb&freeformpage=Merge%20Client CollabNet Merge Client for Subclipse] &mdash; take advantage of the new merge cleverness in Subversion 1.5+.


[http://git.or.cz/gitwiki/EclipsePlugin EGit] -- git support
[http://eclipse.org/dltk Dynamic Language Toolkit] &mdash; complete with TCL and Ruby IDEs.


[http://www.eclipse.org/emf EMF] -- Eclipse Modeling Framework
[http://www.eclipse.org/datatools DTP] &mdash; database Development Tools.


[http://www.epic-ide.org/ EPIC] -- Perl tooling
[http://www.eclemma.org/ EclEmma] &mdash; code coverage tool to help you enhance your unit tests.


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


[http://moreunit.sourceforge.net/ MoreUnit] -- Helper for writing more and better unit tests.
[http://www.eclipse.org/emf EMF] &mdash; Eclipse Modeling Framework.


[http://www.eclipse.org/mylyn Mylyn] -- a task-focused UI for Eclipse with bugzilla and trac integration.
[http://www.epic-ide.org/ EPIC] &mdash; Perl tooling.


[http://www.eclipse.org/photran Photran] -- Fortran support for Eclipse
[http://www.eclipse.org/gef GEF] &mdash; Eclipse Graphical Editing Framework (''not'' the [http://www.eclipse.org/vep Visual Editor]).


[http://www.phpeclipse.com/ PHPEclipse] -- PHP tooling
[http://eclipse.org/m2e/ M2E] &mdash; Maven integration for Eclipse.


[http://pydev.sf.net PyDev]
[http://moreunit.sourceforge.net/ MoreUnit] &mdash; Helper for writing more and better unit tests.


[http://bastian-bergerhoff.com/eclipse/features/web/QuickREx/toc.html QuickREx] -- Regular expression tester
[http://www.eclipse.org/mylyn Mylyn] &mdash; 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/specfile/ RPM Specfile Editor]
[http://www.eclipse.org/linuxtools/projectPages/oprofile OProfile]
 
[http://www.eclipse.org/ptp Parallel Tools Platform (PTP)] &mdash; Parallel and Fortran programming support for Eclipse
 
[http://www.eclipse.org/linuxtools/projectPages/perf/ Perf]


[http://www.eclipse.org/linuxtools/projectPages/rpmstubby/ RPM Specfile Generator] -- This plugin makes packaging other plugins really easy.
[http://www.phpeclipse.com/ PHPEclipse] &mdash; PHP Development Tooling.


[http://oss.tresys.com/projects/setools Eclipse SETools] -- SELinux policy analysis tools
[http://pydev.sf.net PyDev] &mdash; Python IDE for Eclipse.


[http://sourceforge.net/projects/shelled Shelled] -- Editor for shell scripts
[http://bastian-bergerhoff.com/eclipse/features/web/QuickREx/toc.html QuickREx] &mdash; regular expression tester.


[http://oss.tresys.com/projects/slide SLIDE] -- SLIDE is an integrated development environment (IDE) for Security Enhanced Linux (SELinux) developers and integrators
[http://www.eclipse.org/linuxtools/projectPages/specfile/ RPM Specfile Editor]


[http://subclipse.tigris.org Subclipse] -- support for working with Subversion repositories
[http://www.eclipse.org/linuxtools/projectPages/rpmstubby/ RPM Specfile Generator] &mdash; this plugin makes packaging other plugins really easy.


[http://oss.tresys.com/projects/setools Eclipse SETools] &mdash; SELinux policy analysis tools.


Coming soon in rawhide:
[http://sourceforge.net/projects/shelled Shelled] &mdash; editor for shell scripts.


[http://www.eclipse.org/birt BIRT] [https://bugzilla.redhat.com/show_bug.cgi?id=485424 review request]
[http://oss.tresys.com/projects/slide SLIDE] &mdash; SLIDE is an integrated development environment (IDE) for Security Enhanced Linux (SELinux) developers and integrators.


[http://www.eclipse.org/datatools DTP] <s>[https://bugzilla.redhat.com/show_bug.cgi?id=484676 review request]</s>
[http://subclipse.tigris.org Subclipse] &mdash; support for working with Subversion repositories.


[http://www.eclipse.org/linuxtools/projectPages/oprofile OProfile]
[http://www.eclipse.org/linuxtools/projectPages/valgrind SystemTap GUI]


[http://stapgui.sourceforge.net/ SystemTap GUI] [https://bugzilla.redhat.com/show_bug.cgi?id=483205 review request]
[http://www.eclipse.org/swtbot/ SWTBot] &mdash; UI and functional testing tool for SWT and Eclipse based applications.


[http://www.eclipse.org/linuxtools/projectPages/valgrind Valgrind]
[http://www.eclipse.org/linuxtools/projectPages/valgrind Valgrind]


== Plug-ins We'd Like To Ship ==
[http://eclipse.org/webtools/ Webtools] &mdash; Eclipse WTP project (mostly packaged).
* 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
* Valgrind
** <s>needs BIRT</s>
** review request:  [https://bugzilla.redhat.com/485941 485941]
** see [[Features/EclipseProfilingTools]]
* OProfile
** review request: 
** see [[Features/EclipseProfilingTools]]
* [http://eclipse.org/vep VE]
** requested [https://bugzilla.redhat.com/show_bug.cgi?id=473779 here]
** it seems kind of dead upstream


== Plug-ins Which Need Packaging Work ==
== Plugins Which Need Packaging Work ==
* BIRT
[https://bugzilla.redhat.com/show_bug.cgi?id=970145 Mylyn Reviews (RFE)]
** all of it needs <s>DTP and</s> WTP
** Tracker bug to get WTP built (filed against BIRT since that's what needs it) [https://bugzilla.redhat.com/486369 486369]
* DTP
** Tracker bug to get all of DTP built:  [https://bugzilla.redhat.com/show_bug.cgi?id=485460 485460]
** Package of [http://sourceforge.net/projects/lpg/ lpgjavaruntime] [https://bugzilla.redhat.com/486365 486365]
** Fix build with lucene 2 and submit it upstream [https://bugzilla.redhat.com/486366 486366]
** <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


== Contact ==
== Contact ==
Line 125: Line 114:
== Testing ==
== 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] .
Eclipse ships it's tests as a subpackage called eclipse-tests. Install it via `yum install eclipse-tests` and launch /usr/bin/eclipse-runEclipsePackageTests.
 
All test results will be saved and available for later analysis. Note: Not all tests finish successfully for now.


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


# <tt>$ svn co http://dev.eclipse.org/svnroot/technology/org.eclipse.linuxtools/sdktests/3.4.1/Fedora eclipse-sdk-tests</tt>
The way Eclipse and its plugins are installed in Fedora differs from the way this is done upstream. This can
# <tt>$ cd eclipse-sdk-tests</tt>
sometimes lead to installation problems in Fedora. We are working on a solution to make installations
# <tt>$ ./build.sh</tt>
more robust in future Fedora releases. In the meantime however, this section is meant to help you troubleshoot those problems.
# (... wait for build)
The main theme is "I updated eclipse and my plugins no longer show up".
# <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.
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:


== Plans ==
<pre>
We plan to ship the Eclipse SDK (<tt>eclipse</tt> SRPM) version [http://www.eclipse.org/eclipse/development/freeze_plan_3_4_2.php 3.4.2] in Fedora 11. A Fedora 10 update will also followOther [http://www.eclipse.org/ganymede/ Ganymede] release train projects should be updated to their [http://wiki.eclipse.org/index.php/Ganymede_Simultaneous_Release#Coordinated_Service_Releases Ganymede "Service Release 2"] releases when they are available.  We are using the following tracker bug for updating to 3.4.2:
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.


[https://bugzilla.redhat.com/show_bug.cgi?id=486350 https://bugzilla.redhat.com/486350]
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>


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


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:
<pre>
diff `find /usr/lib*/eclipse/ -name bundles.info` `find ~/.eclipse/ -name bundles.info` | grep "<" | sed s/"< "/""/ >> `find ~/.eclipse/ -name bundles.info`
</pre>


* [https://bugzilla.redhat.com/show_bug.cgi?id=485488 Autotools] (included under CDT umbrella)
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.
* [https://bugzilla.redhat.com/show_bug.cgi?id=486356 BIRT]
Please file a bug which includes the diff.
* [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 problemsWe will of course have to coordinate testing them all.
== Plans ==
We ship the Eclipse SDK (<tt>eclipse</tt> SRPM) version 4.3.0 in Fedora 19Other [http://www.eclipse.org/kepler/ Kepler] release train projects are also updated to their Helios versions.


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


== References ==
== References ==


* [http://www.redhat.com/magazine/018apr06/features/eclipse_foox/ Introduction to Eclipse on Fedora]
* None currently
* [http://www.redhat.com/magazine/018apr06/features/eclipse_tromey/ Confessions of an Eclipse convert]
* [http://www.gotmono.com/docs/ide/eclipse.html Eclipse for developing Mono applications]


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

Revision as of 12:32, 6 February 2020

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 NT. It is maintained and used by a large community of volunteers and companies.

It is shipped in Fedora (>= 4). Plugins are continuously being added to Fedora. The Fedora packaging team aims to take care of Eclipse plugin review requests quickly. Packaging guidelines for Eclipse plugins can be found here: Packaging/EclipsePlugins.

Installation

It can be installed via merely running:

sudo dnf install eclipse

If you run into an error with glassfish-el you might be seeing bug 1759176 and you'll need to enable the Eclipse module first, then install eclipse.

sudo dnf module enable eclipse:latest
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 many plugins (see below). We are working on making plugin packaging easier (see RPM Stubby and Fedora Packager for Eclipse).

Would you like to help?

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

Plugins We Ship

Autotools (part of CDT SRPM)

BIRT

CMakeed — editor for CMake files

CDT — C/C++ Development Tooling.

ChangeLog

CollabNet Merge Client for Subclipse — take advantage of the new merge cleverness in Subversion 1.5+.

Dynamic Language Toolkit — complete with TCL and Ruby IDEs.

DTP — database Development Tools.

EclEmma — code coverage tool to help you enhance your unit tests.

EGit — support for working with Git repositories.

EMF — Eclipse Modeling Framework.

EPIC — Perl tooling.

GEF — Eclipse Graphical Editing Framework (not the Visual Editor).

M2E — Maven integration for Eclipse.

MoreUnit — Helper for writing more and better unit tests.

Mylyn — a task-focused UI for Eclipse with bugzilla and trac integration. See also Eclipse Mylyn Red Hat Bugzilla setup instructions and Eclipse Mylyn packaging guide for more Mylyn related information.

OProfile

Parallel Tools Platform (PTP) — Parallel and Fortran programming support for Eclipse

Perf

PHPEclipse — PHP Development Tooling.

PyDev — Python IDE for Eclipse.

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

SWTBot — UI and functional testing tool for SWT and Eclipse based applications.

Valgrind

Webtools — Eclipse WTP project (mostly packaged).

Plugins Which Need Packaging Work

Mylyn Reviews (RFE)

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

GNU Classpath Wiki

Planet Classpath

GCJ - GNU Compiler for Java

Testing

Eclipse ships it's tests as a subpackage called eclipse-tests. Install it via yum install eclipse-tests and launch /usr/bin/eclipse-runEclipsePackageTests.

All test results will be saved and available for later analysis. Note: Not all tests finish successfully for now.

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.

Plans

We ship the Eclipse SDK (eclipse SRPM) version 4.3.0 in Fedora 19. Other Kepler release train projects are also updated to their Helios versions.

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

References

  • None currently