[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [p2-dev] new bundle in the maintenance branch

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...


Susan Franklin McCourt <susan_franklin@xxxxxxxxxx>
Sent by: p2-dev-bounces@xxxxxxxxxxx

11/18/2009 07:37 PM

Please respond to
P2 developer discussions <p2-dev@xxxxxxxxxxx>

P2 developer discussions <p2-dev@xxxxxxxxxxx>
[p2-dev] new bundle in the maintenance branch

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).

The related bugs are


The project set has been updated so you should be able to reload it.
UI tests are passing

Some of the rcp examples have not been updated yet, so don't be concerned if they are not compiling.
The relevant patches to PDE and WST can be found in


p2-dev mailing list