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 Minutes - 20090210"
| Line 5: | Line 5: | ||
** This information gets used by the p2 engine to update the launcher.ini. | ** This information gets used by the p2 engine to update the launcher.ini. | ||
** Discussed having it in the source only or binary also. If we include in the source it will help our builds. We need to consider if it should be in the binary. | ** Discussed having it in the source only or binary also. If we include in the source it will help our builds. We need to consider if it should be in the binary. | ||
| − | ** Does p2.inf put actions in the IU or should we use a new CU? | + | ** Does p2.inf put actions in the IU or should we use a new CU? Should we allow the p2.inf to be able to specify where the actions go? |
| + | ** Should develop the p2 tutorial to see how this fits together. Need to figure out how to recommend the CU for simple configurator to start is brought into a custom product. | ||
* Equinox status message | * Equinox status message | ||
Revision as of 15:43, 10 February 2009
Agenda
- Review provisional API conventions for Equinox
- concurrent bundle in the SDK
- p2.inf to launcher fragments (bug 263783)
- This information gets used by the p2 engine to update the launcher.ini.
- Discussed having it in the source only or binary also. If we include in the source it will help our builds. We need to consider if it should be in the binary.
- Does p2.inf put actions in the IU or should we use a new CU? Should we allow the p2.inf to be able to specify where the actions go?
- Should develop the p2 tutorial to see how this fits together. Need to figure out how to recommend the CU for simple configurator to start is brought into a custom product.
- Equinox status message
Attendees
- Andrew
- Matthew
- Tom
- Pascal
- Simon
- DJ
- John
- Jeff?