|[cross-project-issues-dev] Indigo checklist "jarred bundles" vs. org.eclipse.pde.ui.samples|
Hi, While iterating through the Indigo checklist I'm stuck at the "jarred bundles" item. The reason is pretty simple: we provide extensions to org.eclipse.pde.ui.samples which can't work off a jarred bundle (see bug 332748). Going by the letter this requires us ask the Tools PMC to ask the Planning Council for an exception, right? This feels strange, given that providing a bundle with samples shouldn't be an exception. Are we using an outdated extension point (is there a replacement?)? Or, positively thinking, should we (you and me) join forces in order to get the bug fixed? thanks, Stephan PS: While I'm at it: I had a hard time making any sense of the "capabilities" requirement. After reading "hundreds" :) of bug comments and some blog posts it seems to boil down to: we need to document a string pattern that will capture our relevant UI contributions, so that product builders can use this pattern to specify the capabilities they like to see configurable, right? If that's the message I'd love to see the requirement rephrased, or a link to a simple explanation added. But still: how can I advise product builders that our capabilities require, e.g., the Java Development capability given that "the" Java Development capability doesn't exist, except in the SDK product. So decoupling capabilities from projects/artifacts means we have no names for referring to other project's capabilities. I must be missing something, no?
Back to the top