Difference between revisions of "Equinox p2 1.0 Technical Specs"

Revision as of 22:13, 29 October 2007

Tooling

modification of the build infrastructure to produce artifact and metadata repos

Priority: 1

modification of the product build to produce p2 eanbled products

Priority: 1

tasks wrappering the metadata generator

Priority: 1

tasks wrappering the director application

Priority: 1

generation of artifact / metadata repo from the content of the workspace

Priority: 1

provision on launch

Priority: 1

target provisioner reading the bundles.txt

Priority: 1

target provisioner reading the profile

Priority: 2

target provisioner invoking the user UI to provision into the target (if it is associated with a profile) Priority: 3

integration of the repository browsing UI into a PDE/p2 view

Priority: 2

converter from site.xml to p2 categories

Priority: 1

repository edition to publish / remove artfiacts and metadata

Note: This is necessary if we don't want people to start messing around with the content of the file directly

Priority: 1

target to read bundles.txt

Priority: 1

target to read profiles

Priority: 2

target provisioning UI

Priority: 3

Metadata generator advises

Site optimizer

How does the source gets provisioned in the target

User interaction

Have a preference to allow for automatic download before installation

Have a preference to silent installation

Need a way to identify a license uniquely

A way to present remembered licenses

A way to present remembered signatures

Better presentation of licenses

Support for installation even when there are errors in the configuration

Priority: 2

Download technology

Adaptative download manager

Priority: 2

MD5 / SHA1 processing steps

Priority: 1

Delta processing step

Priority: 1

Transparent selection of artifact repository

Priority: 1

Pack 200 support

==Core technologies==

Response file

Priority: 2

provide infrastructure to remember accepted signers per profile

Priority: 1

provide infrastructure to remember accepted licenses per profile

Priority: 1

support for invoking the engine on a phase basis

Priority: 1

governor

Priority: 1

need a way to express the governor permissions

Priority: 1

Need a way to ensure that a bundle pool is only used by one agent to avoid problems with GC

Priority: 1

define how categorization of site is done

Priority: 1

simple configurator policy

framework admin, review the performance on big scenarios

Priority: 1

simple configurator, ensure startup performance

Priority: 1

simple configurator, ensure start level order

Priority: 2

reconciliation with bundles watched from directories

Priority: 1

support to restart failed download.

Priority: 2

phases

Priority: 1

persistence of actions

Priority: 1

support for fixes in the metadata

Priority: 1

support for update in the metadata

Priority: 1

support for sequenced update in the metadata

Priority: 1

translation of metadata

Priority: 1

Discovery of JRE and how do we deal with changing JREs

Priority: 1

make the agent dynamic

Priority: 1

Scalability

Priority: 1

Movable installs

Priority: 1

Variables

Priority: 2

Nested profiles

Priority: 3

Do we need to separate the configuration from the installation

Priority: 1

Locating files in one IU

Priority: 1

Locating files in another IU

Priority: 2

Support to canonicalize version numbers

Priority: 2

Shared agent data access

Priority: 1

Scope which repositories are used for a given operation

Priority: 2

Repositories associated to a profile

Separate meta-level capabilities and requirements from the base level ones

Priority: 1

Expression of dependencies

policy to purge the rollback registry

Priority: 1

support for the rollback registry to keep track of why there is this entry in it

Priority: 1

Artifact garbage collector

Priority: 1

Metadata garbage collector

Priority: 1

directory watcher policies

Three variations:

• call Director.install() and potentially generate metadata (Priority: 1)
• to call FwkAdmin.addBundle() (Priority 2)
• to call BundleContext.installBundle() (Priority 2)

shared installs

Priority: 1

sharing of bundles across eclipses

Priority: 1

Ability to share the agent data across multiple running processes

Priority: 1

Support for undo-ing an operation after an agent crash

Priority: 1

Support continuing of an engine operation upon restart of the agent

Priority: 1

Support for DBCS in repos, in install path and other Uis

Priority: 1

Support for multiple bundle artifacts in one IU

Priority: 2

Review the concept of flavor and the default flavor we ship

Priority: 1

Refine the concept of marker

Priority: 1

Ability for touchpoint to cause a runtime to be started / stopped / restarted

Priority: 1

Do we need to have a mechanism to replace the UM policy files

Priority: 1

Ability to update eclipse.exe

Priority: 2

Ability to specify multiple bundle pools

Priority: 1

Installing bundles in a non running eclipse

Priority: 1

Repositories

Have a way to allow repositories to refer to others (this means mirrors or not)

Priority: 1

embedded repos

Priority: 1

published repos

Priority: 1

Ability to publish artifacts with known processing steps

Priority: 1

Have a repo within a jar for a given bundle

Priority: 1

Authentication to connect to a repository

Priority: 1

Implement ways to have trusted repositories

Priority: 1

Dependency on other Eclipse components

(Platform) support to get the proxy / socks from the OS

(ECF) ECF make sure proxy / socks settings are honored properly

(ECF) Support for https

(ECF) Authentication to connect to an http server

(ECF) Exchange of certificates on connection

(Security) Storage of certificates

(Security) Storage of login information in a session

(Platform) Markup for dynamic bundles

UM Compatibility

Do we have to keep delivering the features?

How do we deal with platform.xml?

Do we allow for the installation of old style update site content through the new UI

Do we leave the old API?

Do we change UM to produce a bundles.txt instead of a platform.xml

Review the different UM policies and how they map/apply in the new world