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 Minutes - 20081216"
(→Agenda) |
|||
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
== Attendees == | == Attendees == | ||
| + | |||
| + | * Andrew Cattle | ||
| + | * Andrew Niefer | ||
| + | * DJ Houghton | ||
| + | * John Arthorne | ||
| + | * Oleg Besedin | ||
| + | * Pascal Rapicault | ||
| + | * Tom Watson | ||
== Agenda == | == Agenda == | ||
| + | |||
* UNC path support | * UNC path support | ||
* M5 - are we on track for major features implementations | * M5 - are we on track for major features implementations | ||
* API freeze | * API freeze | ||
* Transforms issues | * Transforms issues | ||
| − | + | * Start levels | |
| − | + | ||
== Minutes == | == Minutes == | ||
| + | |||
| + | * Plan update | ||
| + | ** Everyone should send status on items on the [http://www.eclipse.org/projects/project-plan.php?projectid=rt.equinox Equinox plan] to Tom. | ||
| + | * UNC Path support | ||
| + | ** We didn't support UNC paths very well in 3.4 | ||
| + | ** Significant effort is likely needed to address this, but there has been very little demand for it | ||
| + | ** Minimally should try to fail gracefully if we don't support it | ||
| + | * Composite applications | ||
| + | ** Tom gave an overview of composite application framework progress | ||
| + | ** There was some brainstorming of how p2 would interact with a composite application hierarchy | ||
| + | * API freeze | ||
| + | ** Little or no API work left to do for 3.5, so we are on track for API freeze | ||
| + | * Transforms | ||
| + | ** Currently transforms are bundles, but considering making them framework extensions instead | ||
| + | ** We have problems on startup because the transform bundles are not starting early enough when using simpleconfigurator. | ||
| + | ** If the registry bundle starts before the transforms, then the transforms are not applied | ||
| + | ** Can workaround the problem by tweaking start levels | ||
| + | * Start levels | ||
| + | ** Currently PDE build magically hard-codes start-levels and auto-start settings for various well-known bundles | ||
| + | ** There is now support in 3.5 for setting start levels and auto-start in the product file | ||
| + | ** The p2 publisher would need to duplicate the magic start level computation for well known bundles at metadata generation time | ||
| + | ** Would like to remove the "magic" from PDE build and consume start levels from the product files, but how do we set default values so that user's products don't break | ||
| + | ** One option is for PDE UI to copy start levels from the target platform into the product file when a bundle/feature is added to a product at development time | ||
| + | ** Likely still need compatibility mode for handling old product files that don't contain start level data | ||
Latest revision as of 16:08, 16 December 2008
Attendees
- Andrew Cattle
- Andrew Niefer
- DJ Houghton
- John Arthorne
- Oleg Besedin
- Pascal Rapicault
- Tom Watson
Agenda
- UNC path support
- M5 - are we on track for major features implementations
- API freeze
- Transforms issues
- Start levels
Minutes
- Plan update
- Everyone should send status on items on the Equinox plan to Tom.
- UNC Path support
- We didn't support UNC paths very well in 3.4
- Significant effort is likely needed to address this, but there has been very little demand for it
- Minimally should try to fail gracefully if we don't support it
- Composite applications
- Tom gave an overview of composite application framework progress
- There was some brainstorming of how p2 would interact with a composite application hierarchy
- API freeze
- Little or no API work left to do for 3.5, so we are on track for API freeze
- Transforms
- Currently transforms are bundles, but considering making them framework extensions instead
- We have problems on startup because the transform bundles are not starting early enough when using simpleconfigurator.
- If the registry bundle starts before the transforms, then the transforms are not applied
- Can workaround the problem by tweaking start levels
- Start levels
- Currently PDE build magically hard-codes start-levels and auto-start settings for various well-known bundles
- There is now support in 3.5 for setting start levels and auto-start in the product file
- The p2 publisher would need to duplicate the magic start level computation for well known bundles at metadata generation time
- Would like to remove the "magic" from PDE build and consume start levels from the product files, but how do we set default values so that user's products don't break
- One option is for PDE UI to copy start levels from the target platform into the product file when a bundle/feature is added to a product at development time
- Likely still need compatibility mode for handling old product files that don't contain start level data