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.
Difference between revisions of "Equinox p2 1.0 Features"
(→Tooling) |
(→User Interaction) |
||
| Line 18: | Line 18: | ||
== User Interaction == | == User Interaction == | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
; '''Directory monitoring''' | ; '''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 | : 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 | ||
| + | ; '''Drag and drop installation''' | ||
| + | : Users can install new function by dragging and dropping the related files (JARs, directories, zips, ...) on a running Eclipse. Priority: 1 | ||
| + | ; '''Browser-based installation''' | ||
| + | : Installation of new function can be triggered by users clicking on a link in a browser. Priority: 2 | ||
| + | ; '''Update scheduling and policies''' | ||
| + | : p2 supports a number of update policies allowing users to, for example, set update polling periods, have detected updates automatically downloaded, downloaded and installed, etc. Priority: 1 | ||
| + | ; '''Headless operation''' | ||
| + | : All p2 function is accessible through command-line or code interfaces. Complete installation operations can be performed without a graphical user interface. Some operations support the use of response files to silently provide input. Priority: 2 | ||
| + | ; '''???? Remembered licenses''' | ||
| + | : Users are able to accept licenses and not be asked each time such ''remembered'' licenses are encountered. The set of remembered licenses is managed through a preference page that allows for licenses to be added and removed. Priority: 1 | ||
; '''Remembered signers''' | ; '''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 | : 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 | ||
Revision as of 09:45, 30 October 2007
Contents
Tooling
- Generation of p2 repositories at build time
- The PDE build mechanism produces metadata and artifact repositories as part of the normal build. Priority: 2
- Generation of p2 enabled products at build time
- The PDE build mechanism produces all of the p2 related artifacts and metadata (e.g., install registry, profile, ...) when RCP apps are being built. This allows applications deployed as zips to be p2 enabled out of the box.
- Ant task to produce repositories
- N/A Priority: 1
- Ant task to provision products
- N/A Priority: 1
- Streamlined p2 self-hosting
- PDE incrementally and continuously produces p2 metadata and artifact information based on the contents of the workspace and target platform. This simplifies the development of p2-enabled applications by eliminating the need for time-consuming deployment and export cycles while testing and allowing developers to install bundles directly from their workspace without exporting or deploying. Priority: 2
- Provisioning the target
- PDE's Target Provisioner mechanism has been extended to allow the use of p2 when adding bundles to the target platform. This allows bundle developers to benefit from all facilities in p2 when managing their targets. Priority: 3
- Repository browsers and editors
- p2 tooling includes browsers and editors for the artifact and metadata repositories. Users can view, add and remove elements from local and remote p2 repositories. Priority: 2
- Migration tools
- Developers can deploy existing features and Eclipse product configurations into p2 repositories using p2 Publisher tools that automatically transform runtime and Update Manager markup into p2 data structures and add this data and artifacts to the relevane repositories. Priority: 2
User Interaction
- 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
- Drag and drop installation
- Users can install new function by dragging and dropping the related files (JARs, directories, zips, ...) on a running Eclipse. Priority: 1
- Browser-based installation
- Installation of new function can be triggered by users clicking on a link in a browser. Priority: 2
- Update scheduling and policies
- p2 supports a number of update policies allowing users to, for example, set update polling periods, have detected updates automatically downloaded, downloaded and installed, etc. Priority: 1
- Headless operation
- All p2 function is accessible through command-line or code interfaces. Complete installation operations can be performed without a graphical user interface. Some operations support the use of response files to silently provide input. Priority: 2
- ???? Remembered licenses
- Users are able to accept licenses and not be asked each time such remembered licenses are encountered. The set of remembered licenses is managed through a preference page that allows for licenses to be added and removed. 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