Detailed Description

Benefit to Fedora

Scope

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

ensure we have all dependent packages updated and OSGi-ified a la Orbit

(eclipse.org/orbit)

ensure secondary arches can still build and run

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`. Hopefully we'll be able to ensure that 3rd party plugins they've installed (into `~/.eclipse`) will continue to work.

Dependencies

`sat4j` (I have an SRPM I will submit for review ASAP)

ECF (To be called `eclipse-ecf` and has other dependencies of its own). We'll at least need these ECF bundles:

`org.eclipse.ecf.filetransfer_2.0.0.v20080611-1715.jar`

`org.eclipse.ecf.identity_2.0.0.v20080611-1715.jar`

`org.eclipse.ecf.provider.filetransfer.ssl_1.0.0.v20080611-1715.jar`

`org.eclipse.ecf.provider.filetransfer_2.0.0.v20080611-1715.jar`

`org.eclipse.ecf.ssl_1.0.0.v20080611-1715.jar`

`org.eclipse.ecf_2.0.0.v20080611-1715.jar`

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

Contingency Plan

Stick with Eclipse 3.3.2.

Documentation

Release Notes

We may need a release note if we don't get user-installed plugins working.