(→Scope) |
(→Scope) |
||
Line 40: | Line 40: | ||
# eclipse-swt '''DONE''' | # eclipse-swt '''DONE''' | ||
# eclipse-gef '''DONE''' | # eclipse-gef '''DONE''' | ||
# eclipse-rse '''DONE''' | |||
Todo: | Todo: | ||
Line 58: | Line 59: | ||
# eclipse-rpm-editor | # eclipse-rpm-editor | ||
# eclipse-rpmstubby | # eclipse-rpmstubby | ||
# eclipse-shelled | # eclipse-shelled | ||
# eclipse-subclipse | # eclipse-subclipse |
Revision as of 12:03, 9 July 2010
Fedora 14 Eclipse Helios Update
Summary
Update Fedora's Eclipse stack to Helios releases.
Owner
- Name: Alex Kurtakov, Andrew Overholt
- Email: akurtako at redhat, overholt at redhat
Current status
- Targeted release: Fedora 14
- Last updated: 2010-07-09
- Percentage of completion: 45%
Detailed Description
Many Eclipse projects release annually in June. The 2010 version of this simultaneous release is known as "Helios" and is made up of 39 projects and 33 million lines of code. The foundation of these projects is the Eclipse project itself, producing the Eclipse SDK which contains the Eclipse Platform, the Eclipse Java Development Tools (JDT), and the Eclipse Plugin Development Environment (PDE).
This Fedora feature encompasses the updating of the Eclipse packages in Fedora to be their Helios versions. Note that not all eclipse-* packages in Fedora are hosted at eclipse.org which coordinates the simultaneous release so this feature does not include them (notable examples include PyDev which is shipped in Fedora as eclipse-pydev).
Benefit to Fedora
The latest and greatest versions of Eclipse packages will be available to Fedora users.
Scope
Update dependencies (see below), many eclipse-* packages, and test upgrade experience from existing Galileo (2009 simultaneous release name) versions. The packages (SRPM names) that will be updated include:
Done:
- eclipse DONE
- eclipse-jdt DONE
- eclipse-pde DONE
- eclipse-platform DONE
- eclipse-rcp DONE
- eclipse-swt DONE
- eclipse-gef DONE
- eclipse-rse DONE
Todo:
- eclipse-birt
- eclipse-callgraph
- eclipse-cdt
- eclipse-changelog
- eclipse-dltk
- eclipse-dtp
- eclipse-egit
- eclipse-emf
- eclipse-jgit
- eclipse-linuxprofilingframework
- eclipse-mylyn
- eclipse-oprofile
- eclipse-photran (merged with eclipse-ptp which is up for review)
- eclipse-pydev
- eclipse-rpm-editor
- eclipse-rpmstubby
- eclipse-shelled
- eclipse-subclipse
- eclipse-systemtapgui
- eclipse-testframework
- eclipse-valgrind
How To Test
- x86 or x86_64 hardware is preferred for testing as the OpenJDK JIT (just in time compiler) is present there
- Installing the packages listed above in the "Scope" section should be installed
- Eclipse should start from the GNOME menu under Programming or from the command line
- The Eclipse Help system should display and allow clicking around the contents (Help menu -> Help Contents)
- Help -> About should show 3.6 somewhere as the version
- Functionality of plugins should be verified but this is plugin-specific
- eclipse-* should upgrade cleanly from their Galileo versions
User Experience
Expected to remain largely the same.
Dependencies
Notable Eclipse SDK dependencies include:
- icu4j DONE
- sat4j DONE
- jetty (jetty requires a new version of maven to build) DONE
These dependencies are almost complete but updates are not yet in rawhide. There are few packages that depend on the Eclipse stack outside of eclipse-*.
Contingency Plan
Non-completion will result in the F13 versions from the Galileo release being used in F14.