Features/Eclipse34

= Eclipse 3.4 =

Summary
Re-base to Eclipse 3.4 (Ganymede). What's new for this release? In addition to bug fixes and general improvements, there are some interesting new features. For example, there is the Equinox/p2 provisioning framework which replaces the old update manager. The new update manager is a lot easier for the end-user to update and maintain the workbench. In the JDT, multicore support has been added to ensure Eclipse is fast as possible for compiling Java code in the future. As well, a new feature called Plug-in Spy has been added which is a useful tool for plug-in developers to determine what plug-in supplies a selection class.

Owner

 * Name: Andrew Overholt

Current status

 * Targeted release:  Fedora 10
 * Last updated: 2008-09-16 by Jeff Johnston
 * Percentage of completion: 100%
 * Outstanding issues:
 * tag build in koji
 * get p2 user UI working
 * get builds going on non-upstream platforms
 * get p2-ization stuff into package-build and eclipse-* %install sections
 * run tests
 * re-build icu4j, sat4j, tomcat5, and eclipse-*

Detailed Description

 * The Eclipse project releases its IDE and development platform once a year. The most recent release in June 2008 is version 3.4 also known as Ganymede.  A lot of improvements and functional additions appear in 3.4.

Benefit to Fedora
The latest bells and whistles :)

Scope
See 452875
 * use p2
 * decide (with other distros and in consultation with upstream) about dropins location
 * update pdebuild.sh to generate p2 metadata
 * ensure our metadata is properly read by p2 if we're going to use the dropins approach for additional plugins
 * ensure our arch-specific/arch-independent split still works move everything in the SDK to %{_libdir}/eclipse
 * ensure we have all dependent packages updated and OSGi-ified a la Orbit
 * get sat4j reviewed
 * ensure secondary arches can still build and run ppc64 works. I assume other arches will also work.

Test Plan
Automated upstream tests, daily usage, 3rd party plugin installation

User Experience
The user should see a seamless upgrade from `eclipse-*-3.3.2` to `eclipse-*-3.4.0`. Unfortunately, 3rd party plugins users have installed (into `~/.eclipse`) will probably no longer work without re-installation (see Eclipse.org bug 223434.

Dependencies

 * `sat4j` (Review Request Done.)
 * OSGi-ifying: `objectweb-asm` (probably with a sub-package, `objectweb-asm-eclipse` or something)
 * get a mega-asm bundle from the multiple JARs we have in Fedora now
 * the rest of the dependencies from Eclipse 3.3 except Tomcat (actually, still need Tomcat for the servlet{,.jsp} API and jasper sub-packages)

JARs we'll need to have to be able to symlink
These are all the JARs in the source drop. The source ones will be generated by the build so ignore those.

Contingency Plan

 * Stick with Eclipse 3.3.2.

Documentation

 * http://help.eclipse.org

Release Notes
We will need a release note stating that user-installed plugins from earlier releases will need to be re-installed for 3.4.

Comments and Discussion

 * See Talk:Features/Eclipse34