Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Equinox p2 1.0 Features
Contents
Tooling
Generation of p2 sites at build time
Description: The build mechanism allows to produce metadata repositories and artifact repositories as part of the build.
Priority: 2
Generation of p2 enabled products at build time
Description: The build mechanism allows the production of all the p2 related "artifacts" (install registry, profile, …) as part of the build when RCP apps are being built. This will allow for the application created to be p2 provisionable.
Ant task to produce repositories
Description: N/A
Priority: 1
Ant task to provision products
Description: N/A
Priority: 1
Streamlined p2 selfhosting
Description: This is the ability to test the deployment of Installable Units without having to go through a full export cycle.
Priority: 2
Provision the target
Description: This allows to provision Installable Units directly in the target by going through a full provisioning experience
Priority: 3
Repository browser
Description: Offer the ability to browse the content of a metadata or artifact repository.
Priority: 2
Repository editor
Description: Offer the ability to edit the content of a repository: publish / remove.
Priority: 2
User Interaction
Automatic download before installation
Description: When an update is being detected, the download happens in the background and the user is only prompted to install once the download is complete
Priority: 1
Browser integration
Description: Clicking on a link in a browser should cause the installation of the IUs in eclipse
Priority: 2
Remembered licenses
Description: The dialog presenting licenses gives the ability to the user to accept a license forever. The remembered licenses can be revoked through a preference page. Revoking a license will not cause the uninstallation of the software.
Priority: 1
Silent updates
Description: The user should have the ability to have all updates happen completely transparently and just be prompted for restart
Priority: 1
Headless installation
Description: Complete installation can be performed without a UI. Certain installation will require the usage of a response file.
Priority: 2
Drag and drop installation
Description: The user could install Installable Units by drag and drop an archive on the window of a running Eclipse
Priority: 1
Directory monitoring
Description: In order to improve the management of plug-ins, the user could install Installable Units by drag and drop an archive on the window of a running Eclipse. Several mode of installation could be supported: direct call to BundleContext.installBundle(), FwkAdmin.installBundle(), Director.install().
Priority: 1
Remembered signers
Description: The dialog presenting signatures should give the ability to trust this signer forever. The remembered signers can be revoked through a preference page. Revoking a license will not cause the uninstallation of the software.
Priority: 1
Download technology
Automatic detection of proxy / socks from the OS / Browser
Description: Proxies and socks settings available in the OS should be detected and automatically set in Eclipse
Priority: 2
Automatic selection of mirrors
Description: When mirrors are available, the
best mirror is always being picked.
Priority: 1
Adaptative downloads
Description: The download will adapt on the characteristic of the connection, servers and other criterias (parallel download, choice of what is being downloaded (delta, pack200, …), etc.)
Priority: 1
Download integrity through MD5 / SHA1
Description: The integrity of the artifacts downloaded will be verified using either MD5 / SHA1 algorithms
Priority: 1
Delta-ing
Description: Ability to publish deltas of an artifact instead of full artifacts
Priority: 1
Transparent restart
Description: After the abortion of an installation, artifacts that have been fully downloaded will not be downloaded again (unless a GC happened) and the downloads of partially downloaded artifacts will be picked up where it left.
Priority: 2
Secure transport (https, …)
Description: Support secure connection to http
Priority: 1
Automatic retries
Description: When an artifact can not be found in a given repository retries will be done and in case of repeated failures another mirror will be picked if available
Priority: 1
Download time estimation
Description: Estimation of the download time as the download progresses
Priority: 2
Jar signature check
Description: Signed jars being downloaded will be verified
Priority: 1
Pack200
Description: Support to download pack200'd artifacts to cut the download size
Priority: 1
Trusted repositories
Description: p2 should have the ability to identify trusted repositories against others. The trust could be done through an exchange of keys.
Priority: 2
Support for proxy / socks connection
Description: p2 transports will honour proxy and socks settings
Priority: 1
Referencing additional repositories (mirror or supplement)
Description: Repositories will be able to reference additional repositories, such that the addition of the first one to the system could cause the additional ones.
Priority: 1
Support for login into repositories
Description: p2 will honour servers requesting authentication
Priority: 1
Media support (CDs)
Description: p2 will allow repositories to be stored on medias such as CDs, DVDs.
Priority: 1
Security
IU signature
Description: IUs carry a signature to ensure their content has not been tempered with
Priority: 3
Support for login into repositories
Description: p2 will honour servers requesting authentication
Priority: 1
Trusted repositories
Description: p2 should have the ability to identify trusted repositories against others. The trust could be done through an exchange of keys.
Priority: 1
Secure transport (https, …)
Description: Support secure connection to http
Priority: 1
Jar signature check
Description: Signed jars being downloaded will be verified Priority: 1
Trusted repositories
Description: p2 should have the ability to identify trusted repositories against others. The trust could be done through an exchange of keys.
Priority: 2
Core technologies
Permission based control of provisioning operation
Description: When a provisioning operation is performed, permissions will be checked to ensure that it is acceptable to do it in the given context.
Priority: 1
General model of dependencies
Description: Installable Units will be able to express dependencies on things other than other Installable Units (e.g. memory available on the machine, etc.).
Priority: 1
Shared installs
Description: Scenarios where the installation of eclipse is shared across multiple users is streamlined.
Priority: 1
Sharing of bundles across systems
Description: Multiple eclipse instances share the bundle jars in one common location (aka bundle pool), thus making the installation faster and the required disk footprint smaller
Priority: 1
Garbage collection of unused bundles
Description: Bundles being shared across multiple instances of eclipse will be garbage collected when they are no longer in use. A retention policy will be applied.
Priority: 1
Create new installs without re-downloading all the artifacts
Description: p2 is able to create a brand new install of a product already installed with minimal or no download depending on the retention policy of the garbage collector.
Priority: 1
Resilience to install problems
Description: p2 provides a best effort approach to ensure that failed installations do not leave the system in an inconsistent state.
Priority: 1
OS integration
Description: p2 provides support for a tighter desktop integration
Priority: 2
Support to deliver fixes
Description: Support to deliver fixes
Priority: 1
Sequenced udpate
Description: Allows to express that one particular update has to applied on the path to another one.
Priority: 2
Fine grain installation of IUs
Description: Allow for the installation of Groups as well as single IUs
Priority: 2
Install in a non running system
Description: Allow to install IUs into an Eclipse that is not running
Priority: 1
Installability of another state
Description: Previous states of the system are being kept to allow for recreation of a setup used in the past. It could allow for installing somebody else state.
Priority: 1
Revert to the previous install
Description: When an installation has succeeded but the result is not satisfactory it should be possible to revert the system to the "exact" same state as it was before.
UM Compatibility
Content of 3.3 styles update site will be installable without change Description: Update site created with former versions of eclipse will be installable