Bug 95193 - [Workbench] org.eclipse.ui.components.services ext pt is marked as experimental
Summary: [Workbench] org.eclipse.ui.components.services ext pt is marked as experimental
Status: VERIFIED DUPLICATE of bug 127167
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.0   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: 3.2 M5   Edit
Assignee: Boris Bokowski CLA
QA Contact:
URL:
Whiteboard:
Keywords: api
Depends on:
Blocks:
 
Reported: 2005-05-13 14:14 EDT by Jim des Rivieres CLA
Modified: 2006-02-14 16:07 EST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jim des Rivieres CLA 2005-05-13 14:14:38 EDT
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&apos;t use it. It 
will be removed soon.
      </documentation>
   </annotation>
Comment 1 Jim des Rivieres CLA 2005-05-13 14:17:51 EDT
Also, there also a dubious reference in the handlers.exsd:

"The handlers extension point is an elaboration of the experimental 
&lt;code&gt;handlerSubmission&lt;/code&gt; element defined in Eclipse 3.0".

Please clarify/correct.
Comment 2 Kim Horne CLA 2005-05-13 14:52:16 EDT
Adding doug for the second question
Comment 3 Douglas Pollock CLA 2005-05-13 14:56:04 EDT
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.
Comment 4 Jim des Rivieres CLA 2005-05-13 15:09:16 EDT
Doug,  What became of it? Did it go away, or become official 3.1 API, or is it 
still experimental?
Comment 5 Douglas Pollock CLA 2005-05-13 15:12:13 EDT
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?
Comment 6 Jim des Rivieres CLA 2005-05-13 15:17:37 EDT
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?
Comment 7 Douglas Pollock CLA 2005-05-13 15:26:45 EDT
It is possible that someone could be using the 3.0 experimental form, but there
is a complete replacement.
Comment 8 Jim des Rivieres CLA 2005-05-13 15:36:12 EDT
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? 
Comment 9 Douglas Pollock CLA 2005-05-13 15:41:06 EDT
I've added Bug 95217 to track this separate issue.  Leaving this bug to deal
with the components work.
Comment 10 Stefan Xenos CLA 2005-05-13 17:03:12 EDT
What is the approprate form for an internal extersion point? How about:

"This extension point is internal. Don't use it."
Comment 11 Jim des Rivieres CLA 2005-05-14 11:36:38 EDT
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
Comment 12 Boris Bokowski CLA 2006-02-02 23:01:52 EST
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?
Comment 13 Douglas Pollock CLA 2006-02-03 07:32:35 EST
Yes, it is safe to delete the schema and any references to it.
Comment 14 Boris Bokowski CLA 2006-02-13 11:07:23 EST
It turns out that Nick has already removed the remaining bits.

*** This bug has been marked as a duplicate of 127167 ***
Comment 15 Boris Bokowski CLA 2006-02-14 16:07:37 EST
[I20060214-0800]

Verfied on Windows XP.