Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: for the plan.

Jump to: navigation, search

Equinox/Meeting Minutes/20100105


  • Need to check M5 Plan Status
  • Status for Wednesday team meeting
  • 3.5.2 engame topics
  • Uses use
  • Build breakage wrt aspectj repo


  • Jeff McAffer
  • DJ Houghton
  • John Arthorne
  • Tom Watson
  • Simon Kaegi
  • Andrew Niefer
  • Pascal Rapicault


M5 Plan Status

  • Jan 29 is M5
  • all non-p2 related topics are in fair shape
  • p2 things are coming along. The API branch is going to be integrated next week.
  • p2 API work will not be "done" on integration but all major things should be done
  • a lot of work but on track
  • server side filter work is going in today
  • p2 server side work


  • team should send Tom status for the weekly message

3.5.2 endgame topics

  • A few changes have been going in
  • There are a few outstanding bugs that will be looked at
  • Should coordinate with ECF. Pascal will open a bug and follow up

Uses use

  • a few projects out there are using "uses"
  • and a few have packages that export packages that are included in the VM
  • there is a clash between require-bundle and the uses.
  • for example, the core.runtime bundle reexports OSGi which exports all the JRE classes
  • look at e4's use of core.runtime (they should not be using much/any) see bug 271834
  • possibly look at duplicating core.runtime to core.runtime.legacy to eliminate the re-exports

Build breakage wrt aspectj repo

  • Aspect J team updates their repo rather then adding to it so our builds fail
  • this causes problems for the weaving work in Equinox
  • need to have stable repos
  • there is a requirement to have a retention policy for each project as to how they manage dev builds
  • Equinox team needs to set the example here to ensure that people can be successful in similar situations

Back to the top