Project Plan For Eclipse Packaging Project, version 1.1
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. 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 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
Release Milestones
All EPP releases appear simultaneously with the release train releases (here: Galileo).
| Galileo M1 - no EPP builds | n/a | |
| Galileo M2 - no EPP builds | n/a | |
| Galileo M3 - to be discussed: EPP builds necessary? | n/a | |
| Galileo M4 | 2009-01-08 | |
| Galileo M5 | 2009-02-12 | |
| Galileo M6 | 2009-03-20 | |
| Galileo M7 | 2009-05-08 |
All packages must be defined and their content must be specified. |
| Galileo RC1 | 2009-05-21 | |
| Galileo RC2 | 2009-05-28 | |
| Galileo RC3 | 2009-06-04 | |
| Galileo RC4 | 2009-06-11 | |
| Galileo RC5 | 2009-06-18 |
Target Environments
EPP creates its packages for Windows 32-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
Compatibility with Previous Releases
Themes and Priorities
Galileo 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
Galileo Packages
- 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
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.