Equinox/p2/Meetings/20081215

Agenda

• New Collector 256355 256411
• Interfaces for metadata types 256359
• UNC paths 207103
• API expectations for Galileo
• Publisher migration
• Version types

Attendees

• Andrew Cattle
• Andrew Niefer
• Darin Wright
• Dave Stevenson
• DJ Houghton
• Doug Schaefer
• Henrik Lindberg
• Ian Bull
• Jeff McAffer
• John Arthorne
• Pascal Rapicault
• Scott Lewis
• Simon Kaegi
• Susan McCourt
• Tom Hallgren

Minutes

• Plan
  • Draft M5 plan is available
  • There is currently a large list of changes that people want to make, which is risking hitting our M5 goals
• Repository robustness
  • Still need a mechanism for automated testing of misbehaving servers (hangs, error codes, etc)
• Collector
  • Still investigating, have looked through all existing collectors to get a better idea of usage patterns
  • Currently looks like the query needs to wrap the collector passed to the query because the passed in collector does things like wrapping the query result in other objects
• Interfaces for metadata types
  • Patch provided that creates interfaces for metadata types
  • Looking at artifact API to see if further changes needed
  • May be places in the p2 code that makes assumptions about the concrete implementation types for metadata API
  • Should be almost no references to the existing concrete classes when done
  • Deprecate the concrete classes to help people fix their references to the concrete classes
• UNC paths
  • What is the impact of not supporting UNC paths
  • Need to communicate with PMC and wider community - no point others working on UNC path support if p2 can't even support it at install-time
• API expectations for Galileo
  • Is there any targeted areas where API would be valuable
  • If we're not producing API, or producing very little, we need to let people know to avoid surprises
• Publisher integration
  • Aiming to replace use of metadata generator in PDE build with new publisher applications
  • Need to figure out how to publish branded launchers from a product file
  • Aim to have the bits in place by end of M5 to enable using the publisher instead of the generator
  • Still support the metadata generator applications and Ant tasks in compatibility mode (forward to publisher)
• Pluggable versions
  • Problem with expressing/handling pluggable version in resolver (see ResolutionHelper)
  • Currently heavily use BundleDescription class from OSGi resolver, which doesn't support pluggable version types
  • We had a long discussion about whether to have only a canonical versioning scheme in the metadata, versus encoding the version semantics alongside the version number in the metadata
  • Henrik/Thomas to iterate the proposal based on today's discussion