This kind of "common dumping ground"
bundle worries me - what usually happens is that it ends up pulling in
a big list of dependencies as more services are added, and then anyone
who needs a single one of those services pulls in everything. Are there
more examples of things we want to put here in the near term? The two services
that are there today could easily be put in the org.eclipse.equinox.p2.metadata
bundle (it adds two classes, very little code, and no extra dependencies).
The only weird dependency is that TranslationSupport depends on the engine.
I think that could easily be refactored by having an internal hook for
the "default locale query" that the engine bundle plugs into
when it starts. We already have about 30 bundles which seems like more
than enough granularity for all the different deployment scenarios we are
interested in...

Hi, everyone.
I added a new bundle today, org.eclipse.equinox.p2.common, after talking
to Pascal. We needed a home for utility stuff that is above the core and
underneath the UI. I didn't want the p2.operations bundle to become a grab
bag of utils just because it lives in the same space as the utils (above
core, under UI).