Community
Participate
Working Groups
3.1 M7 The org.eclipse.ui.components.services ext pt is marked as experimental and internal and about to be removed. Please clarify its status. o.e.ui.components/schema/services.mxsd <?xml version='1.0' encoding='UTF-8'?> <!-- Schema file written by PDE --> <schema targetNamespace="org.eclipse.ui.components"> <annotation> <appInfo> <meta.schema plugin="org.eclipse.ui.components" id="services" name="Component services"/> </appInfo> <documentation> EXPERIMENTAL: This extension point is internal. Don't use it. It will be removed soon. </documentation> </annotation>
Also, there also a dubious reference in the handlers.exsd: "The handlers extension point is an elaboration of the experimental <code>handlerSubmission</code> element defined in Eclipse 3.0". Please clarify/correct.
Adding doug for the second question
Jim: The handlerSubmission element shipped in 3.0 as experimental, and was only ever used by the workbench internally. Whether this was a valid thing to do is a moot point now; that's what happened.
Doug, What became of it? Did it go away, or become official 3.1 API, or is it still experimental?
Jim: It got marked as "deprecated" (using the new PDE deprecation mechanism for schema elements) but still exists. I figured it would be inappropriate to remove it entirely. Is this wrong?
Doug, Since the ext. pt. was marked experimental in 3.0, we are not committed to keeping it alive. It will depend entirely on the details of the situation. Do we think anyone might be using it in its experimental 3.0 form? Do we have a replacement in 3.1?
It is possible that someone could be using the 3.0 experimental form, but there is a complete replacement.
Doug, Given that we have a complete replacement, I believe we should remove the old experimental extension point for 3.1, fix up the reference to point to its replacement, and add an entry to the 3.1 Migration Guide explaining what we did. While we're at it, do we have any other deprecated experimental APIs in the same boat?
I've added Bug 95217 to track this separate issue. Leaving this bug to deal with the components work.
What is the approprate form for an internal extersion point? How about: "This extension point is internal. Don't use it."
For internal extension points: - document the extension point normally in extension schema - start the doc with "This extension point is intended to be used internally to the Eclipse Platform. Client should not use." - name the extension point "internalXXX" to make it very clear - do not include generated extension schema doc in plug-in developer guide
Doug, can I delete the extension point and the extensions referring to the component framework from org.eclipse.ui's plugin.xml? It is referring to nonexisting code, isn't it?
Yes, it is safe to delete the schema and any references to it.
It turns out that Nick has already removed the remaining bits. *** This bug has been marked as a duplicate of 127167 ***
[I20060214-0800] Verfied on Windows XP.