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/Location selection scenarios"
m (Missing Features in Equinox p2 Update UI moved to Equinox/p2/Location selection scenarios: The original page title was too broad.) |
|||
| Line 1: | Line 1: | ||
| − | This page tries to collect | + | This page tries to collect scenarios and use cases for controlling the various locations used by p2. This includes managing the location initial location of a profile, p2's data area, shared locations, the location into which additional function is installed and the relationship to the bundle pool etc. |
| + | Each details a scenario and is followed by one or more approaches. In some cases the scenario is not currently supported and a bug report may be listed. | ||
== Install == | == Install == | ||
=== Select Bundle Pool on Install === | === Select Bundle Pool on Install === | ||
| + | ''<Note: This needs to be recast as a scenario. Why would they be unhappy? What are they expecting when setting this location?>'' | ||
It should be possible to select the target bundle pool when installing plug-ins in Eclipse. The functionality can be compared to selecting an extension location when installing plug-ins prior to Equinox p2. | It should be possible to select the target bundle pool when installing plug-ins in Eclipse. The functionality can be compared to selecting an extension location when installing plug-ins prior to Equinox p2. | ||
It is mainly motivated by user control to help driving user satisfaction. If you take control away from a user, it will make him/her unhappy. Therefore, a user should be able to keep control over the layout/organization of software on his computer. Additionally, the concept of extension locations has been well adopted within Eclipse. For example, PDE allows to compose plug-ins in wizards, dialogs and editors by grouping plug-ins based on their install locations. | It is mainly motivated by user control to help driving user satisfaction. If you take control away from a user, it will make him/her unhappy. Therefore, a user should be able to keep control over the layout/organization of software on his computer. Additionally, the concept of extension locations has been well adopted within Eclipse. For example, PDE allows to compose plug-ins in wizards, dialogs and editors by grouping plug-ins based on their install locations. | ||
| + | |||
[[Category:Equinox p2]] | [[Category:Equinox p2]] | ||
Revision as of 11:28, 2 January 2009
This page tries to collect scenarios and use cases for controlling the various locations used by p2. This includes managing the location initial location of a profile, p2's data area, shared locations, the location into which additional function is installed and the relationship to the bundle pool etc.
Each details a scenario and is followed by one or more approaches. In some cases the scenario is not currently supported and a bug report may be listed.
Install
Select Bundle Pool on Install
<Note: This needs to be recast as a scenario. Why would they be unhappy? What are they expecting when setting this location?>
It should be possible to select the target bundle pool when installing plug-ins in Eclipse. The functionality can be compared to selecting an extension location when installing plug-ins prior to Equinox p2.
It is mainly motivated by user control to help driving user satisfaction. If you take control away from a user, it will make him/her unhappy. Therefore, a user should be able to keep control over the layout/organization of software on his computer. Additionally, the concept of extension locations has been well adopted within Eclipse. For example, PDE allows to compose plug-ins in wizards, dialogs and editors by grouping plug-ins based on their install locations.