From Fedora Project Wiki
Line 32: Line 32:


== User Experience ==
== 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 continue to work (see [https://bugs.eclipse.org/bugs/show_bug.cgi?id=223434 Eclipse.org bug 223434].
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 [https://bugs.eclipse.org/bugs/show_bug.cgi?id=223434 Eclipse.org bug 223434].


== Dependencies ==
== Dependencies ==

Revision as of 14:50, 30 June 2008

Eclipse 3.4

Summary

Re-base to Eclipse 3.4 (Ganymede).

Owner

Current status

  • Targeted release: Fedora 10
  • Last updated: 2008-06-25
  • Percentage of completion: 10%

Detailed Description

Benefit to Fedora

The latest bells and whistles :)

Scope

See 452875

  • Upgrade/introduce dependencies (see below)
  • 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
  • ensure we have all dependent packages updated and OSGi-ified a la 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. Unfortunately, 3rd party plugins users have installed (into ~/.eclipse) will probably no longer work without re-installation (see Eclipse.org bug 223434.

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

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.

JAR filename Containing package More info
com.ibm.icu_3.8.1.v20080530.jar icu4j Upgrade to 3.8.1?
com.jcraft.jsch_0.1.37.v200803061811.jar jsch Ensure we have the proper version and MANIFEST.MF data.
javax.servlet.jsp_2.0.0.v200806031607.jar tomcat5-servlet-2.4-api Ensure we have the proper MANIFEST.MF data.
javax.servlet_2.4.0.v200806031604.jar tomcat5-jsp-2.0-api Ensure we have the proper MANIFEST.MF data.
org.apache.ant_1.7.0.v200803061910/lib/* ant I think we're good here.
org.apache.commons.el_1.0.0.v200806031608.jar jakarta-commons-el I think we're good here.
org.apache.commons.logging_1.0.4.v20080605-1930.jar jakarta-commons-logging I think we're good here.
org.apache.jasper_5.5.17.v200806031609.jar tomcat5-jasper-eclipse We have 5.5.26 but upstream ships against 5.5.17. We may need to see if anything has a hard version requirement on 5.5.17.
org.apache.lucene.analysis_1.9.1.v20080530-1600.jar lucene Ensure 2.3.x we have in Fedora still works.
org.apache.lucene_1.9.1.v20080530-1600.jar lucene Ensure 2.3.x we have in Fedora still works.
org.eclipse.ecf.filetransfer_2.0.0.v20080611-1715.jar eclipse-ecf SRPM to be created.
org.eclipse.ecf.identity_2.0.0.v20080611-1715.jar eclipse-ecf SRPM to be created.SRPM to be created.
org.eclipse.ecf.provider.filetransfer.ssl_1.0.0.v20080611-1715.jar eclipse-ecf SRPM to be created.
org.eclipse.ecf.provider.filetransfer_2.0.0.v20080611-1715.jar eclipse-ecf SRPM to be created.
org.eclipse.ecf.ssl_1.0.0.v20080611-1715.jar eclipse-ecf SRPM to be created.
org.eclipse.ecf_2.0.0.v20080611-1715.jar eclipse-ecf SRPM to be created.
org.eclipse.osgi/osgi/osgi.cmpn.jar internal to Eclipse Ensure unnecessary for build.
org.eclipse.osgi/osgi/osgi.core.jar internal to Eclipse Ensure unnecessary for build.
org.eclipse.osgi/supplement/osgi/osgi.jar internal to Eclipse Ensure unnecessary for build.
org.eclipse.swt.tools/swttools.jar internal to Eclipse Ensure unnecessary for build.
org.eclipse.swt.win32.win32.x86/swt.jar internal to Eclipse Ensure unnecessary for build.
org.eclipse.swt/extra_jars/exceptions.jar internal to Eclipse Ensure unnecessary for build.
org.junit4/junit.jar junit4 I think we're fine here.
org.junit_3.8.2.v20080602-1318/junit.jar junit I think we're fine here.
org.mortbay.jetty_5.1.14.v200806031611.jar jetty Upgrade to 5.1.14?koji link for 5.1.14. Verify new build has proper OSGi data in MANIFEST.MF.
org.objectweb.asm_3.1.0.v200803061910.jar objectweb-asm Need to get monolithic OSGi-ified JAR OR patch pde.api to use the multiple jars (and will have to add OSGi MANIFEST.MFs to them). The vast majority of the imports are included in asm-3.1.jar but two are in asm-tree-3.1.jar and one is in asm-util-3.1.jar. See this file for more details.
org.sat4j.core_2.0.0.v20080602.jar sat4j SRPM to be submitted for review.
org.sat4j.pb_2.0.0.v20080602.jar sat4j SRPM to be submitted for review.

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.