Project Plan For Eclipse Packaging Project, version 1.3

Introduction

The Eclipse Packaging Project (EPP) is responsible for creating technology that makes it easier for new users to consume the output of other Eclipse projects and for coordinating the package releases together with the yearly release train. In order to achieve this goal, EPP is active on different levels since the Europa Release 2007:

  • Create entry level downloads based on defined user profiles. The project defined and created the EPP downloads of Java Developer, Java EE Developer, C/C++ Developer and RCP Developer. These downloads are available from the main Eclipse download page. In addition to that, EPP coordinates with other package maintainers the creation of new package definitions and ensures that the packages are tested.
  • Provide and integrate the EPP Usage Data Collector (UDC). The Usage Data Collector collects information about how individuals are using the Eclipse platform. The intent is to use this data to help committers and organizations better understand how developers are using Eclipse.
  • Provide and integrate the Eclipse Marketplace Client (MPC). The MPC provides tight install integration between the Eclipse workspace and Eclipse Marketplace, plus other third party solution listings.
  • Provide a platform that allows the creation of packages (zip/tar downloads) from an update site. The core technology of the project will enable the creation of download packages that are created by bundling Eclipse features from one or multiple Eclipse update sites.
  • Create and manage a new dynamic installer. EPP creates a new RAP-based wizard that enables a user to choose and pick software components from other Eclipse projects. The output is a customized p2-installer that guides the user through the initial install process and downloads the necessary software components.

Release Deliverables

Table of Contents

Release Milestones

All EPP releases appear simultaneously with the release train releases (here: Helios).

Helios M62010-03-19
Helios M72010-05-07

All packages must be defined and their content must be specified.

Helios RC12010-05-21
Helios RC22010-05-28
Helios RC32010-06-04
Helios RC42010-06-11
Helios RC52010-06-23

Table of Contents

Target Environments

EPP creates its packages for Windows 32-bit, Windows 64-bit, Linux 32-bit, Linux 64-bit and Mac OSX. All of the packages require at least a JVM 1.5 because of the software components that are included in the packages.

Source code used and developed within the project needs a JVM 1.5 or higher.

Internationalization

All outputs produced are prepared for internationalization via Babel.

Table of Contents

Compatibility with Previous Releases

All frameworks and APIs produced with this release are compatible with previous releases

Table of Contents

Themes and Priorities

Helios Packages

EPP will create and deliver the packages for the next release train. The exact content and the number of packages are subject to change and depend on the community feedback and help.

  • Committed
    • Eclipse IDE for Java EE Developers
    • Eclipse IDE for Java Developers
    • Eclipse IDE for C/C++ Developers
    • Eclipse Modeling Tools
    • Eclipse for RCP/Plug-in Developers
    • Eclipse IDE for Java and Report Developers
    • Eclipse IDE for PHP Developers
    • Pulsar for Mobile Java Developers
    • Eclipse SOA Platform for Java and SOA Developers
    Some xhtml content here. Make sure to use the prefix before the elements

Dynamic Package Delivery Component

The dynamic package delivery component provides an extensible framework for, and an exemplary implementation of, a service for dynamically selecting and downloading/installing installable units.

  • Committed

    Preview available for Friends-of-Eclipse.

Usage Data Collector (UDC)

Bug fixes only are planned for this release.

  • Committed

    • udc dialog keeps coming up [295332] (target milestone: 1.3.0)
    • Provide the UDC as a Downloadable ZIP archive [220792] (target milestone: 1.3.0)
    • Add link on upload wizard to UDC FAQ [235693] (target milestone: 1.3.0)
    • mismatch between UDC Preferences and the Help that comes with it [252259] (target milestone: 1.3.0)
    • UDC: Upload url should be displayed in preferences/wizard [282382] (target milestone: 1.3.0)
    • Add a link to the usage data collector home page [216975] (target milestone: 1.3.0)
    • Provide source for UDC [221104] (target milestone: 1.3.0)
    • AskUserUploaderWizard shouldn't implement INewWizard [235706] (target milestone: 1.3.0)
    • UDC defaults to 60 second upload period if number formatted incorrectly [284288] (target milestone: 1.3.0)
    • Usage Data Collector is uploading too many files [291796] (target milestone: 1.3.0)
    • Update UDC Releng to use Athena [301767] (target milestone: 1.3.0)
    • Usage data upload fails with proxy requiring authentication [241511] (target milestone: 1.3.0)

Marketplace Client (MPC)

The Marketplace Client will be introduced with this release.

  • Committed

    New code.

Table of Contents

Appendix

Table of Contents

view raw xml of project plan
from project meta-data key "projectplanurl"