Orbit Minutes 070403
- Call convened at 1000 EDT
- Call-in: 613.287.8000 or 866.362.7064, passcode 892048#
- Previous Meeting: Orbit Minutes 070313
- Martin Oberhuber
- David Williams
- Tom Watson
- Hubert Leung
- Jeff McAffer
- Pascal Rapicault
- Simon Kaegi
- Kim Moir
- DJ Houghton
Review action items from last call
IP Log info
A draft of an IP log document was reviewed by Jeff and Pascal and will be sent to the dev list for comments. The intent is for the document to live in the HEAD stream for each project and contain the appropriate IP info for all streams.
- [Orbit IP Log] wiki page created.
- People have been adding comments to page.
- Action: DJ to start working on page generation from log files
- Action: People to comment on wiki as to what they'd like to see on the generated pages
Orbit Map Files
To remove ambiguity created from combining map files from products with the ones produced by Orbit, we would like to ensure that the Orbit-produced map files always have a version for each map file entry. Is this possible?
- Yes. Done.
Update features and map files
David to update the Orbit build process and try multi-versions in the map files. If everything works out he will combine the map and feature files. Note: Does this mean we are down to 1 feature.xml and 1 map file now?
- Yes. Done. We now only have one map file and one feature file. Yeah!!
There are some open issues with the Xerces bundle around splitting the API bundle into mutliple JARs.
Other discussion topics
Originally in Orbit we created a bundle called
org.apache.tools.ant because it is the Orbit naming convention to use the dominant package name as the bundle name. We have determined that there are just too many people using Ant in scripts and other ways that we did not anticipate. It is recommended that we grandfather Ant and leave the
org.apache.ant bundle name.
- [Message] sent to the Orbit mailing list describing the problem.
- People voted on the mailing list (no -1's)
- No objections on the call.
- Action: DJ to rename bundle to be
Modification of 3rd party bundles
How should we handle modifications to our 3rd party bundles. For an example of a use-case see:
Chkpii errors - https://bugs.eclipse.org/bugs/show_bug.cgi?id=177330
Should bundles be exploded or manifest edited - https://bugs.eclipse.org/bugs/show_bug.cgi?id=180354
Should we not condition prebuilt bundles? - https://bugs.eclipse.org/bugs/show_bug.cgi?id=178723