Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
View | Details | Raw Unified | Return to bug 140175
Collapse All | Expand All

(-)porting/3.2/faq.html (+23 lines)
Lines 16-21 Link Here
16
<h1>Eclipse 3.2 Plug-in Migration FAQ</h1>
16
<h1>Eclipse 3.2 Plug-in Migration FAQ</h1>
17
<ol>
17
<ol>
18
	<li><a href="#legacyActionWithNoLabel">Legacy Action With No Label</a></li>
18
	<li><a href="#legacyActionWithNoLabel">Legacy Action With No Label</a></li>
19
	<li><a href="#qualifiedIDs">Usage of IDs with dots (&quot;.&quot;) in Extension Points, Extensions, and Content Types</a></li>
19
</ol>
20
</ol>
20
<h2><a name="legacyActionWithNoLabel">Legacy Action With No Label</a></h2>
21
<h2><a name="legacyActionWithNoLabel">Legacy Action With No Label</a></h2>
21
<p>
22
<p>
Lines 32-37 Link Here
32
In the case of actions appearing in the tool bar, sometimes neither a definition
33
In the case of actions appearing in the tool bar, sometimes neither a definition
33
id nor a label were specified.
34
id nor a label were specified.
34
</p>
35
</p>
36
37
<h2><a name="qualifiedIDs">Usage of IDs with dots (&quot;.&quot;) in Extension Points, Extensions, and Content Types</a></h2>
38
<p> In the past, IDs specified for the extension points, extensions, and content types were expected 
39
to be &quot;simple IDs&quot; with no dots in them (e.g., &quot;myPoint&quot;, not &quot;my.Point&quot;, 
40
not &quot;myPlugin.myPoint&quot;). This rule was specified, but not enforced.</p>
41
<p> In the release 3.2 we added processing of fully-qualified IDs (e.g., &quot;org.eclipse.myPlugin.myPoint&quot;). 
42
However, it turned out that some components had previously used IDs with dots and the change broke 
43
functionality provided by those components. To preserve backward compatibility for IDs of extension points 
44
and extensions, we added special processing based on the version of the XML file:</p>
45
<p><ul>
46
<li>If the XML file has the tag &lt;?eclipse version=&quot;3.0&quot;?&gt;, the runtime
47
functionality remains the same as before (plug-in ID is added to the simple name)</li>
48
<li>If the XML file has the tag &lt;?eclipse version=&quot;3.2&quot;?&gt;, the IDs with dots are treated as fully qualified 
49
names (no plug-in ID is added to the name).</li>
50
</ul></p>
51
<p> Details can be found in the bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=128866">128866</a>.</p>
52
<p> We recommend switching to the 3.2 format as the usage of IDs with dots was never intended to be supported in 
53
the 3.0 format. (Simply put, there is no guarantee that it works in all cases today or that it will work the same 
54
tomorrow.)</p>
55
<p> This processing of the &lt;?eclipse version&gt; tag applies to IDs of extension points and extensions, but not to 
56
the IDs of content types (see bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=139491">139491</a>).</p>
57
35
</body>
58
</body>
36
59
37
</html>
60
</html>

Return to bug 140175