Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Equinox p2 1.0 Features"

(User Interaction)
(No difference)

Revision as of 22:01, 29 October 2007

Tooling

Generation of p2 sites at build time
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
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
N/A Priority: 1
Ant task to provision products
N/A Priority: 1
Streamlined p2 selfhosting
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
This allows to provision Installable Units directly in the target by going through a full provisioning experience. Priority: 3
Repository browser
Offer the ability to browse the content of a metadata or artifact repository. Priority: 2
Repository editor
Offer the ability to edit the content of a repository: publish / remove. Priority: 2

User Interaction

Automatic download before installation
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
Clicking on a link in a browser should cause the installation of the IUs in eclipse. Priority: 2
Remembered licenses
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
The user should have the ability to have all updates happen completely transparently and just be prompted for restart. Priority: 1
Headless installation
Complete installation can be performed without a UI. Certain installation will require the usage of a response file. Priority: 2
Drag and drop installation
The user could install Installable Units by drag and drop an archive on the window of a running Eclipse. Priority: 1
Directory monitoring
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
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
Proxies and socks settings available in the OS should be detected and automatically set in Eclipse. Priority: 2
Automatic selection of mirrors
When mirrors are available, the best mirror is always being picked. Priority: 1
Adaptative downloads
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
The integrity of the artifacts downloaded will be verified using either MD5 / SHA1 algorithms. Priority: 1
Delta-ing
Ability to publish deltas of an artifact instead of full artifacts. Priority: 1
Transparent restart
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, …)
Support secure connection to http. Priority: 1
Automatic retries
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
Estimation of the download time as the download progresses. Priority: 2
Jar signature check
Signed jars being downloaded will be verified. Priority: 1
Pack200
Support to download pack200'd artifacts to cut the download size. Priority: 1
Trusted repositories
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
p2 transports will honour proxy and socks settings. Priority: 1
Referencing additional repositories (mirror or supplement)
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
p2 will honour servers requesting authentication. Priority: 1
Media support (CDs)
p2 will allow repositories to be stored on medias such as CDs, DVDs. Priority: 1

Security

IU signature
IUs carry a signature to ensure their content has not been tempered with. Priority: 3
Support for login into repositories
p2 will honour servers requesting authentication. Priority: 1
Trusted repositories
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, …)
Support secure connection to http. Priority: 1
Jar signature check
Signed jars being downloaded will be verified. Priority: 1
Trusted repositories
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
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
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
Scenarios where the installation of eclipse is shared across multiple users is streamlined. Priority: 1
Sharing of bundles across systems
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
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
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
p2 provides a best effort approach to ensure that failed installations do not leave the system in an inconsistent state. Priority: 1
OS integration
p2 provides support for a tighter desktop integration. Priority: 2
Support to deliver fixes
Support to deliver fixes. Priority: 1
Sequenced udpate
Allows to express that one particular update has to applied on the path to another one. Priority: 2
Fine grain installation of IUs
Allow for the installation of Groups as well as single IUs. Priority: 2
Install in a non running system
Allow to install IUs into an Eclipse that is not running. Priority: 1
Installability of another state
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
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
Update site created with former versions of eclipse will be installable

Back to the top