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.
Difference between revisions of "Equinox Summit 2007 topics"
| Line 9: | Line 9: | ||
** PDE and "Components." PDE has notions of groups of plug-ins in various places... (target definitions, product files, features, etc...) does it make sense to abstract this concept out a bit so it can be reused by other places. | ** PDE and "Components." PDE has notions of groups of plug-ins in various places... (target definitions, product files, features, etc...) does it make sense to abstract this concept out a bit so it can be reused by other places. | ||
** PDE and Provisioning. How will tooling for provisioning work, what happens to features and update sites? | ** PDE and Provisioning. How will tooling for provisioning work, what happens to features and update sites? | ||
| + | |||
| + | * Scott Lewis | ||
| + | ** Security: Authentication and platform login. Integration of JAAS. Extension points and services for extensibility? | ||
| + | ** Bundle distribution: How to allow component-level (groups of plugins, with various dependencies) be easily distributed/installed? How do (bundle) repositories (e.g. OBR, JSR-something) fit in? | ||
| + | ** Related to bundle distribution: How to support EF project component distribution (without features). | ||
| + | ** Accessing PDE programmatically: Need PDE APIs...e.g. https://bugs.eclipse.org/bugs/show_bug.cgi?id=169340 | ||
Revision as of 11:59, 26 June 2007
- Jeff McAffer
- More contributions. This might be a meta-topic but there are likely tangible steps that the current team can take to be more open to new contributions.
- Security directions. We have new contributions for JAAS, JCA, Keystore etc. Lets talk about where this work will take us
- Services. Prosyst has contributed several new services recently. We should review these with an eye to graduating and integrating them into the main stream.
- PDE build. How can we make it better (incremental, easier to setup, ...) and how will the provisioning work impact build.
- Chris Aniszczyk
- PDE Build. How can we tool PDE Build... in terms of having an easy way to get a user started with an automated build. Similar to how PDE provides a .product file for helping build/package RCP applications, maybe we need something similar for an automated build.
- PDE and "Components." PDE has notions of groups of plug-ins in various places... (target definitions, product files, features, etc...) does it make sense to abstract this concept out a bit so it can be reused by other places.
- PDE and Provisioning. How will tooling for provisioning work, what happens to features and update sites?
- Scott Lewis
- Security: Authentication and platform login. Integration of JAAS. Extension points and services for extensibility?
- Bundle distribution: How to allow component-level (groups of plugins, with various dependencies) be easily distributed/installed? How do (bundle) repositories (e.g. OBR, JSR-something) fit in?
- Related to bundle distribution: How to support EF project component distribution (without features).
- Accessing PDE programmatically: Need PDE APIs...e.g. https://bugs.eclipse.org/bugs/show_bug.cgi?id=169340