|[p2-dev] a minimal UI Policy API for 3.6 - who uses QueryProvider and PlanValidator?|
Right now we do not have a concrete plan to promote any of the p2 UI to API for 3.6.
This is simply a matter of resources/priorities.
I am doing some experimental refactoring to see if there is a very small subset of the currently marked provisional API in the UI that could become API in 3.6. This work is not yet committed to the branch.
The idea is that you shouldn't need to use provisional/internals to launch wizards or do simple UI customization. Thus org.eclipse.equinox.p2.ui.sdk would no longer need to be an "x-friend" of the ui, nor would any of the example applications. The overall goal is described in this bug . Please comment there.
More specifically, I want to make the UI Policy API and keep it as simple as possible. We started out with a lot of flexibility to support both the admin agent and the SDK. My new assumption is that the admin agent (and PDE) would remain "x-friends" of the UI. To this end, I would like to remove the concept of a replaceable QueryProvider and PlanValidator. I don't know of anyone who is using PlanValidator but I know of least one case (Helmut?) where the QueryProvider has been reimplemented. If you are using these classes, please comment in  how you are using them.